myscandalcollection.net Home 18SX asian student picture sex story amateur celebrity farah kayuria video anal chinese gangbang indonesian lessy mixscandal peeping pinay sexy webcam watch western Todays Free Videos Sort by: Latest Most Viewed ...

myscandalcollection.net
  • Domain Name
    myscandalcollection.net
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #43275
  • Page Size
    23.2 KB
  • Ip Address
    108.162.199.84
  • Heading
    H1: 2, H2: 12, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 12 JPG, 0 PNG

Website Meta Analysis

  • Title
    myscandalcollection.net
  • Meta Keyword
  • Meta Description
    myscandalcollection.net Home 18SX asian student picture sex story amateur celebrity farah kayuria video anal chinese gangbang indonesian lessy mixscandal peeping pinay sexy webcam watch western Todays Free Videos Sort by: Latest Most Viewed ...

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.199.84
  • Domain Age
    3 Years, 1 Months, 21 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from myscandalcollection.net.

HTML Analysis

  • server: cloudflare-nginx
  • date: Wed, 13 Feb 2013 13:25:24 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding,User-Agent
  • x-powered-by: PHP/5.2.17
  • x-cf-powered-by: WP 1.3.9
  • x-pingback: http://www.myscandalcollection.net/xmlrpc.php
  • cache-control: max-age=3600
  • x-cacheable: YES
  • x-varnish: 1709083901
  • via: 1.1 varnish
  • age: 0
  • x-cache: MISS
  • cf-ray: 4025644e8f2045b
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
Domain Services Provided By:
domain.com, email
http://www.domain.com

Registrant:
c/o MYSCANDALCOLLECTION.NET
P.O. Box 821650
Vancouver, WA 98682
US

Registrar: Domain.com
Domain Name: MYSCANDALCOLLECTION.NET
Created on: 09-JAN-10
Expires on: 10-JAN-13
Last Updated on: 27-MAR-12

Administrative Contact:
email
c/o MYSCANDALCOLLECTION.NET
P.O. Box 821650
Vancouver, WA 98682
US
+1.360-449-5933

Technical Contact:
email
c/o MYSCANDALCOLLECTION.NET
P.O. Box 821650
Vancouver, WA 98682
US
+1.360-449-5933

Domain servers in listed order:
RUTH.NS.CLOUDFLARE.COM
TOM.NS.CLOUDFLARE.COM

This listing is a Whois Privacy Customer. Mail correspondence to this
address must be sent via USPS Express Mail(TM) or USPS Certified
Mail(R); all other mail will not be processed. Be sure to include
the domain name in the address.

DNS Analysis


DNS servers
tom.ns.cloudflare.com [173.245.59.147]
ruth.ns.cloudflare.com [173.245.58.143]


DNS Records

Answer records
myscandalcollection.net NS  ruth.ns.cloudflare.com 86400s
myscandalcollection.net MX
preference: 0
exchange: direct-connect.myscandalcollection.net
300s
myscandalcollection.net A 108.162.198.84 300s
myscandalcollection.net A 108.162.199.84 300s
myscandalcollection.net SOA
server: ruth.ns.cloudflare.com
email: dns@cloudflare.com
serial: 2012110100
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s
myscandalcollection.net 28 [16 bytes] 300s
myscandalcollection.net 28 [16 bytes] 300s
myscandalcollection.net NS  tom.ns.cloudflare.com 86400s
myscandalcollection.net TXT v=spf1 a mx include:websitewelcome.com ~all 300s

Authority records

Additional records
direct-connect.myscandalcollection.net A 194.145.208.236 300s

IP 108.162.199.84 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 108.162.199.84"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=108.162.199.84?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 108.162.192.0 - 108.162.255.255
    CIDR: 108.162.192.0/18
    OriginAS: AS13335
    NetName: CLOUDFLARENET
    NetHandle: NET-108-162-192-0-1
    Parent: NET-108-0-0-0-0
    NetType: Direct Assignment
    Comment: http://www.cloudflare.com
    RegDate: 2011-10-28
    Updated: 2012-03-02
    Ref: http://whois.arin.net/rest/net/NET-108-162-192-0-1

    OrgName: CloudFlare, Inc.
    OrgId: CLOUD14
    Address: 665 Third Street #207
    City: San Francisco
    StateProv: CA
    PostalCode: 94107
    Country: US
    RegDate: 2010-07-09
    Updated: 2013-01-04
    Comment: http://www.cloudflare.com/
    Ref: http://whois.arin.net/rest/org/CLOUD14

    OrgTechHandle: ADMIN2521-ARIN
    OrgTechName: Admin
    OrgTechPhone: +1-650-319-8930
    OrgTechEmail:
    OrgTechRef: http://whois.arin.net/rest/poc/ADMIN2521-ARIN

    OrgAbuseHandle: ABUSE2916-ARIN
    OrgAbuseName: Abuse
    OrgAbusePhone: +1-650-319-8930
    OrgAbuseEmail:
    OrgAbuseRef: http://whois.arin.net/rest/poc/ABUSE2916-ARIN

    OrgNOCHandle: NOC11962-ARIN
    OrgNOCName: NOC
    OrgNOCPhone: +1-650-319-8930
    OrgNOCEmail:
    OrgNOCRef: http://whois.arin.net/rest/poc/NOC11962-ARIN

    RTechHandle: ADMIN2521-ARIN
    RTechName: Admin
    RTechPhone: +1-650-319-8930
    RTechEmail:
    RTechRef: http://whois.arin.net/rest/poc/ADMIN2521-ARIN

    RNOCHandle: NOC11962-ARIN
    RNOCName: NOC
    RNOCPhone: +1-650-319-8930
    RNOCEmail:
    RNOCRef: http://whois.arin.net/rest/poc/NOC11962-ARIN

    RAbuseHandle: ABUSE2916-ARIN
    RAbuseName: Abuse
    RAbusePhone: +1-650-319-8930
    RAbuseEmail:
    RAbuseRef: http://whois.arin.net/rest/poc/ABUSE2916-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 31 Errors
  • 0 Warnings
Ratio Text/Html
  • 0.7587732232379829
Message Error
  • Error Line 386, Column 16: there is no attribute "hspace"
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 386, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…
  • Error Line 386, Column 25: there is no attribute "vspace"
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 386, Column 25: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…
  • Error Line 386, Column 34: there is no attribute "border"
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 386, Column 34: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…
  • Error Line 386, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …space=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=168…
  • Error Line 386, Column 63: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=168 height=608 scr…
  • Error Line 386, Column 77: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=168 height=608 scrolling=no allo…
  • Error Line 386, Column 85: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=168 height=608 scrolling=no allowtranspa…
  • Error Line 386, Column 96: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=168 height=608 scrolling=no allowtransparency=true …
  • Error Line 386, Column 110: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=168 height=608 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 386, Column 131: there is no attribute "allowtransparency"
    …ht=608 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 386, Column 131: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=608 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 386, Column 140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 386, Column 146: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 386, Column 201: end tag for element "iframe" which is not open
    …parency=true src=http://adserver.juicyads.com/adshow.php?adzone=40070></iframe>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 410, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=720 height=98…
  • Error Line 410, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=720 height=98…
  • Error Line 410, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=720 height=98 scro…
  • Error Line 410, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=720 height=98 scrolling=no allow…
  • Error Line 410, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=720 height=98 scrolling=no allowtranspar…
  • Error Line 410, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=720 height=98 scrolling=no allowtransparency=true s…
  • Error Line 410, Column 91: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …width=0 width=720 height=98 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 410, Column 112: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ght=98 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 410, Column 121: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 410, Column 127: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 410, Column 183: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=145997></iframe>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 411, Column 23: end tag for element "a" which is not open
    <!--JuicyAds END--></a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 480, Column 39: document type does not allow element "meta" here
    <meta content="7758" name="lumfilecom"> 

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 480, Column 40: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta content="7758" name="lumfilecom"> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 480, Column 1: start tag was here
    <meta content="7758" name="lumfilecom"> 

Visitor Analysis

Daily Visitor
  • 3.267 visits
Daily Visitor