Free porn mega site; NEW: Upload sex videos to PORN.COM! Offering incredibility fast XXX video streaming & unlimited downloading of the best hardcore sex videos & the newest adult DVD's. PORN.COM has thousands ...

porn.com
  • Domain Name
    porn.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #593
  • Page Size
    56.3 KB
  • Ip Address
    64.210.140.16
  • Heading
    H1: 1, H2: 3, H3: 5, H4: 2, H5: 0, H6: 0
  • Images
    1 GIF, 50 JPG, 0 PNG

Website Meta Analysis

  • Title
    Free Porn Videos! PORN.COM, XXX Porno & Sex Videos! HD & Mobile!
  • Meta Keyword
    porn,free porn,sex videos,xxx porn,porn tube,free porn videos,porno
  • Meta Description
    Free porn mega site; NEW: Upload sex videos to PORN.COM! Offering incredibility fast XXX video streaming & unlimited downloading of the best hardcore sex videos & the newest adult DVD's. PORN.COM has thousands of tags, amateur all the way up to unique PORN.COM's Exclusive HD videos! Also containing a massive porn pics database! Use the new porn community hub to find, follow, & chat with other porn lovers and even favorite porn stars! Be sure to keep an eye out for special exclusive LIVE PORN.COM cam shows. Be sure to check out the new PORN.COM points system. Now Mobile Device friendly - PORN.COM!

Technical Analysis

  • Webserver
    nginx/1.2.6
  • Ip Address
    64.210.140.16
  • Domain Age
    18 Years, 0 Months, 26 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from porn.com.

HTML Analysis

  • server: nginx/1.2.6
  • date: Mon, 09 Sep 2013 21:05:20 GMT
  • content-type: text/html; charset=utf-8
  • connection: close
  • vary: Accept-Encoding, User-Agent
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: PORN.COM
Registrar: MONIKER

Registrant [2156364]:
Moniker Privacy Services email
Moniker Privacy Services
1800 SW 1st Avenue
Suite 440
Portland
OR
97201
US


Administrative Contact [2156364]:
Moniker Privacy Services email
Moniker Privacy Services
1800 SW 1st Avenue
Suite 440
Portland
OR
97201
US
Phone: +1.5032070147
Fax: +1.9545859186


Billing Contact [2156364]:
Moniker Privacy Services email
Moniker Privacy Services
1800 SW 1st Avenue
Suite 440
Portland
OR
97201
US
Phone: +1.5032070147
Fax: +1.9545859186


Technical Contact [2156364]:
Moniker Privacy Services email
Moniker Privacy Services
1800 SW 1st Avenue
Suite 440
Portland
OR
97201
US
Phone: +1.5032070147
Fax: +1.9545859186


Domain servers in listed order:

NS0.REFLECTED.NET
NS1.REFLECTED.NET

Record created on: 1995-08-19 00:00:00.0
Database last updated on: 2011-07-14 13:46:28.967
Domain Expires on: 2019-01-07 18:02:17.0

DNS Analysis


DNS servers
ns0.reflected.net [66.254.126.2]
ns1.reflected.net [66.254.127.2]


DNS Records

Answer records
porn.com A 64.210.140.16 3600s
porn.com SOA
server: ns0.reflected.net
email: noc@reflected.net
serial: 2013022701
refresh: 10800
retry: 900
expire: 604800
minimum ttl: 86400
3600s
porn.com NS  ns0.reflected.net 3600s
porn.com NS  ns1.reflected.net 3600s
porn.com TXT v=spf1 a:smtp-out.reflected.net a:devilrays-out.reflected.net ip4:66.254.113.78 ip4:208.99.69.22 -all 3600s
porn.com TXT google-site-verification=LvdXU0BGeNfFsTaTJ-0H88Y7QhRf0CvSO37Ev7IXY54 3600s
porn.com TXT google-site-verification=kCw4uuoVI6La1B_eDER4JYuNUcnNnWLxgAv-obhwK2A 3600s
porn.com MX
preference: 0
exchange: smtp-scan01.mx.reflected.net
3600s

Authority records

Additional records
ns0.reflected.net A 66.254.126.2 3600s
ns1.reflected.net A 66.254.127.2 3600s
smtp-scan01.mx.reflected.net A 208.99.91.38 900s

IP 64.210.140.16 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Waltham
  • Continent Code
    02451
  • Latitude
    781
  • Longitude
    506
  • %rwhois V-1.5:002080:00 rwhois.reflected.net (Reflected::RWhoisD 0.0.2)
    network:Class-Name:network
    network:Auth-Area:64.210.128.0/19
    network:ID:NET-64-210-140-16-5455
    network:Handle:NET-64-210-140-16-5455
    network:IP-Network:64.210.140.16/29
    network:IP-Network-Block:64.210.140.16 - 64.210.140.23
    network:Name:GIM Corp
    network:Street-Address:1785 Turner Rd
    network:City:Ontario
    network:State:-- OTHER --
    network:Country-Code:CA
    network:Tech-Email:dugan@netmsi.com
    network:Tech-Phone:519 987 0600
    network:Abuse-Email:dugan@netmsi.com
    network:Abuse-Phone:519 987 0600
    network:Created:20110712
    network:Updated:20110712

    %ok

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 64 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.7965331158577849
Message Error
  • Error Line 46, Column 42: there is no attribute "size"
    …     		<div id="plus"><g:plusone size="small" href="http://www.porn.com"></g:p…

    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 46, Column 55: there is no attribute "href"
    …d="plus"><g:plusone size="small" href="http://www.porn.com"></g:plusone></div>…

    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 46, Column 76: element "g:plusone" undefined
    …ize="small" href="http://www.porn.com"></g:plusone></div>		<p><a class="bookma…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 68, Column 67: cannot generate system identifier for general entity "popunder"
    …lutfinder.com/geo/rotator.php?popup=y&popunder=y&offer=US&source=datingtab" ta…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 68, Column 67: general entity "popunder" not defined and no default entity
    …lutfinder.com/geo/rotator.php?popup=y&popunder=y&offer=US&source=datingtab" ta…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 68, Column 75: reference not terminated by REFC delimiter
    …r.com/geo/rotator.php?popup=y&popunder=y&offer=US&source=datingtab" target="_b…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 68, Column 75: reference to external entity in attribute value
    …r.com/geo/rotator.php?popup=y&popunder=y&offer=US&source=datingtab" target="_b…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 68, Column 75: reference to entity "popunder" for which no system identifier could be generated
    …r.com/geo/rotator.php?popup=y&popunder=y&offer=US&source=datingtab" target="_b…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 68, Column 66: entity was defined here
    …slutfinder.com/geo/rotator.php?popup=y&popunder=y&offer=US&source=datingtab" t…
  • Warning Line 68, Column 78: cannot generate system identifier for general entity "offer"
    …om/geo/rotator.php?popup=y&popunder=y&offer=US&source=datingtab" target="_blan…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 68, Column 78: general entity "offer" not defined and no default entity
    …om/geo/rotator.php?popup=y&popunder=y&offer=US&source=datingtab" target="_blan…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 68, Column 83: reference not terminated by REFC delimiter
    …o/rotator.php?popup=y&popunder=y&offer=US&source=datingtab" target="_blank" re…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 68, Column 83: reference to external entity in attribute value
    …o/rotator.php?popup=y&popunder=y&offer=US&source=datingtab" target="_blank" re…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 68, Column 83: reference to entity "offer" for which no system identifier could be generated
    …o/rotator.php?popup=y&popunder=y&offer=US&source=datingtab" target="_blank" re…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 68, Column 77: entity was defined here
    …com/geo/rotator.php?popup=y&popunder=y&offer=US&source=datingtab" target="_bla…
  • Warning Line 68, Column 87: cannot generate system identifier for general entity "source"
    …tator.php?popup=y&popunder=y&offer=US&source=datingtab" target="_blank" rel="n…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 68, Column 87: general entity "source" not defined and no default entity
    …tator.php?popup=y&popunder=y&offer=US&source=datingtab" target="_blank" rel="n…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 68, Column 93: reference not terminated by REFC delimiter
    …php?popup=y&popunder=y&offer=US&source=datingtab" target="_blank" rel="nofollo…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 68, Column 93: reference to external entity in attribute value
    …php?popup=y&popunder=y&offer=US&source=datingtab" target="_blank" rel="nofollo…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 68, Column 93: reference to entity "source" for which no system identifier could be generated
    …php?popup=y&popunder=y&offer=US&source=datingtab" target="_blank" rel="nofollo…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 68, Column 86: entity was defined here
    …otator.php?popup=y&popunder=y&offer=US&source=datingtab" target="_blank" rel="…
  • Error Line 71, Column 52: there is no attribute "placeholder"
    …="text" value="" name="q" placeholder="Search PORN.COM..." autocomplete="off" …

    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 71, Column 86: there is no attribute "autocomplete"
    …"text" value="" name="q" placeholder="Search PORN.COM..." autocomplete="off" />

    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.

  • Warning Line 275, Column 153: character "&" is the first character of a delimiter but occurred as data
    …Sluts Help Each Other Please One Cock & Share A Cum Kiss" style="background-im…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 276, Column 162: character "&" is the first character of a delimiter but occurred as data
    …Sluts Help Each Other Please One Cock & Share A Cum Kiss" style="text-decorati…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 276, Column 260: character "&" is the first character of a delimiter but occurred as data
    …Sluts Help Each Other Please One Cock &...</a></span>  	<span class="rating" t…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 640, Column 34: cannot generate system identifier for general entity "ct"
    		<img src="/corps.gif?cb=1e2327&ct=787b7d" alt="" />		</p>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 640, Column 34: general entity "ct" not defined and no default entity
    		<img src="/corps.gif?cb=1e2327&ct=787b7d" alt="" />		</p>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 640, Column 36: reference not terminated by REFC delimiter
    		<img src="/corps.gif?cb=1e2327&ct=787b7d" alt="" />		</p>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 640, Column 36: reference to external entity in attribute value
    		<img src="/corps.gif?cb=1e2327&ct=787b7d" alt="" />		</p>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 640, Column 36: reference to entity "ct" for which no system identifier could be generated
    		<img src="/corps.gif?cb=1e2327&ct=787b7d" alt="" />		</p>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 640, Column 33: entity was defined here
    		<img src="/corps.gif?cb=1e2327&ct=787b7d" alt="" />		</p>

Visitor Analysis

Daily Visitor
  • 121.333 visits