h2porn.com

Free porn videos and sex photos linked via thumbnails and archived by category ...

Display Widget for this domain on your website. Click Here
This data was last updated from 17-09-2013 05:22:41  (update).

Overview Info

  • Domain Name
    h2porn.com
  • Favicon
  • Alexa Rank
    #583
  • Google Page Rank
    PR 2
  • Ip Address
    88.85.79.190
  • Page Size
    62.4 KB
  • Images
    1 GIF, 45 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    5 44 0 0 0 0

Website Meta Analysis

  • Title
    Free Porn Videos @ H2Porn
  • Meta Keyword
    free porn videos, free porn, sex videos, porn, sex movies, porn photos, sex tube
  • Meta Description
    Free porn videos and sex photos linked via thumbnails and archived by category

Technical Analysis

  • Webserver
    nginx/1.2.6
  • Ip Address
    88.85.79.190
  • Domain Age
    3 Years, 1 Months, 29 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.2.6
  • date: Tue, 17 Sep 2013 17:22:36 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.3.23
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Direct Privacy ID 42B4C
P.O. Box 6592
Metairie, LA 70009
US
1-504-355-0082


Domain Name: H2PORN.COM

Administrative Contact:
Direct Privacy ID 42B4C, Domain Name Proxy Service, Inc email
P.O. Box 6592
Metairie, LA 70009
US
1-504-355-0082


Technical Contact:
Direct Privacy ID 42B4C, Domain Name Proxy Service, Inc email
P.O. Box 6592
Metairie, LA 70009
US
1-504-355-0082


Record last updated 02-07-2011 05:06:13 AM
Record expires on 08-05-2013
Record created on 08-05-2010

Domain servers in listed order:
NS0.H2PORN.COM 199.101.132.148
NS1.H2PORN.COM 199.101.132.148

DNS Analysis


DNS servers
ns1.h2porn.com [199.101.132.148]
ns0.h2porn.com [199.101.132.148]

DNS Records

Answer records
h2porn.com SOA
server: ns0.h2porn.com
email: hostmaster@h2porn.com
serial: 2011062001
refresh: 3600
retry: 600
expire: 86400
minimum ttl: 3600
86400s
h2porn.com NS  ns0.h2porn.com 86400s
h2porn.com NS  ns1.h2porn.com 86400s
h2porn.com MX
preference: 10
exchange: h2porn.com
86400s
h2porn.com A 199.101.132.148 86400s

Authority records

Additional records
ns0.h2porn.com A 199.101.132.148 86400s
ns1.h2porn.com A 199.101.132.148 86400s
h2porn.com A 199.101.132.148 86400s

IP 88.85.79.190 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 88.85.79.190

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 49 Errors
  • 41 Warnings
Ratio Text/Html
  • 0.7181195458384161
Message Error
  • Error Line 5, Column 68: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

    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 5, Column 1: start tag was here
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  • Error Line 6, Column 115: end tag for "meta" omitted, but OMITTAG NO was specified
    …ree porn videos and sex photos linked via thumbnails and archived by category">

    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 6, Column 1: start tag was here
    <meta name="description" content="Free porn videos and sex photos linked via th…
  • Error Line 7, Column 114: end tag for "meta" omitted, but OMITTAG NO was specified
    …e porn videos, free porn, sex videos, porn, sex movies, porn photos, sex tube">

    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 7, Column 1: start tag was here
    <meta name="keywords" content="free porn videos, free porn, sex videos, porn, s…
  • Error Line 9, Column 88: end tag for "link" omitted, but OMITTAG NO was specified
    …ef="http://static.h2porn.com/styles/main.css" rel="stylesheet" type="text/css">

    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 9, Column 1: start tag was here
    <link href="http://static.h2porn.com/styles/main.css" rel="stylesheet" type="te…
  • Error Line 10, Column 92: end tag for "link" omitted, but OMITTAG NO was specified
    …/rss.php" rel="alternate" type="application/rss+xml" title="Every Day Updates">

    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 10, Column 1: start tag was here
    <link href="/rss.php" rel="alternate" type="application/rss+xml" title="Every D…
  • Warning Line 16, Column 18: character "<" is the first character of a delimiter but occurred as data
    for(var i = 0; i < currentInterval; i++) { top.clearInterval( i ); }

    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 17, Column 14: character "<" is the first character of a delimiter but occurred as data
    for(i = 0; i < currentInterval; i++) { top.clearTimeout( i ); }

    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.
  • Error Line 37, Column 84: end tag for "link" omitted, but OMITTAG NO was specified
    …k rel="shortcut icon" type="image/x-icon" href="http://h2porn.com/favicon.png">

    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 37, Column 1: start tag was here
    <link rel="shortcut icon" type="image/x-icon" href="http://h2porn.com/favicon.p…
  • Warning Line 56, Column 79: cannot generate system identifier for general entity "p"
    …"http://clicks.totemcash.com/?s=29075&p=21&pp=2" rel="nofollow"><span>Desktop …

    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 56, Column 79: general entity "p" not defined and no default entity
    …"http://clicks.totemcash.com/?s=29075&p=21&pp=2" rel="nofollow"><span>Desktop …

    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 56, Column 80: reference not terminated by REFC delimiter
    …http://clicks.totemcash.com/?s=29075&p=21&pp=2" rel="nofollow"><span>Desktop S…

    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 56, Column 80: reference to external entity in attribute value
    …http://clicks.totemcash.com/?s=29075&p=21&pp=2" rel="nofollow"><span>Desktop S…

    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 56, Column 80: reference to entity "p" for which no system identifier could be generated
    …http://clicks.totemcash.com/?s=29075&p=21&pp=2" rel="nofollow"><span>Desktop S…

    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 56, Column 78: entity was defined here
    …="http://clicks.totemcash.com/?s=29075&p=21&pp=2" rel="nofollow"><span>Desktop…
  • Warning Line 56, Column 84: cannot generate system identifier for general entity "pp"
    …://clicks.totemcash.com/?s=29075&p=21&pp=2" rel="nofollow"><span>Desktop Strip…

    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 56, Column 84: general entity "pp" not defined and no default entity
    …://clicks.totemcash.com/?s=29075&p=21&pp=2" rel="nofollow"><span>Desktop Strip…

    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 56, Column 86: reference not terminated by REFC delimiter
    …/clicks.totemcash.com/?s=29075&p=21&pp=2" rel="nofollow"><span>Desktop Strippe…

    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 56, Column 86: reference to external entity in attribute value
    …/clicks.totemcash.com/?s=29075&p=21&pp=2" rel="nofollow"><span>Desktop Strippe…

    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 56, Column 86: reference to entity "pp" for which no system identifier could be generated
    …/clicks.totemcash.com/?s=29075&p=21&pp=2" rel="nofollow"><span>Desktop Strippe…

    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 56, Column 83: entity was defined here
    …p://clicks.totemcash.com/?s=29075&p=21&pp=2" rel="nofollow"><span>Desktop Stri…
  • Error Line 59, Column 31: document type does not allow element "script" here; assuming missing "li" start-tag
    <script type="text/javascript">var addthis_config = {"data_track_clickback":tru…
  • Error Line 61, Column 9: end tag for "li" omitted, but OMITTAG NO was specified
    				</ul>

    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 59, Column 1: start tag was here
    <script type="text/javascript">var addthis_config = {"data_track_clickback":tru…
  • Error Line 75, Column 172: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …ord...') this.value='';" onblur="if(this.value=='') this.value='keyword...';"/>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 76, Column 79: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    					<input type="image" src="http://static.h2porn.com/images/btn_search.gif"/>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 78, Column 12: document type does not allow element "label" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    					<label><input type="radio" name="stype" value="videos" checked="checked" /…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 79, Column 12: document type does not allow element "label" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    					<label><input type="radio" name="stype" value="photos" /> Photos</label>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 86, Column 74: required attribute "alt" not specified
    <img src="http://static.h2porn.com/images/px.jpg" width="1" height="34" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 890, Column 14: there is no attribute "src"
    	<iframe src="http://adv.h2porn.com/adspot.php?spot_id=18" width="160" height="…

    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 890, Column 66: there is no attribute "width"
    …porn.com/adspot.php?spot_id=18" width="160" height="600" frameborder="no" marg…

    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 890, Column 79: there is no attribute "height"
    …ot.php?spot_id=18" width="160" height="600" frameborder="no" marginwidth="0" m…

    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 890, Column 97: there is no attribute "frameborder"
    … width="160" height="600" frameborder="no" marginwidth="0" marginheight="0" sc…

    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 890, Column 114: there is no attribute "marginwidth"
    …ht="600" frameborder="no" marginwidth="0" marginheight="0" scrolling="no" alig…

    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 890, Column 131: there is no attribute "marginheight"
    …der="no" marginwidth="0" marginheight="0" scrolling="no" align="middle" allowt…

    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 890, Column 145: there is no attribute "scrolling"
    …nwidth="0" marginheight="0" scrolling="no" align="middle" allowtransparency="t…

    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 890, Column 156: there is no attribute "align"
    …marginheight="0" scrolling="no" align="middle" allowtransparency="true" align=…

    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 890, Column 183: there is no attribute "allowtransparency"
    …"no" align="middle" allowtransparency="true" align="middle"></iframe><br /><br…

    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 890, Column 196: duplicate specification of attribute "align"
    …o" align="middle" allowtransparency="true" align="middle"></iframe><br /><br />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 890, Column 204: element "iframe" undefined
    …o" align="middle" allowtransparency="true" align="middle"></iframe><br /><br />

    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).
  • Error Line 891, Column 196: duplicate specification of attribute "align"
    …scrolling="no" align="middle" allowtransparency="true" align="middle"></iframe>

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 891, Column 204: element "iframe" undefined
    …scrolling="no" align="middle" allowtransparency="true" align="middle"></iframe>

    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).
  • Error Line 997, Column 31: there is no attribute "language"
    <!-- h2im --><script language=javascript src="http://medleyads.com/spot/14097.h…

    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 997, Column 31: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <!-- h2im --><script language=javascript src="http://medleyads.com/spot/14097.h…
  • Error Line 997, Column 84: required attribute "type" not specified
    …e=javascript src="http://medleyads.com/spot/14097.html"></script><!-- /h2im -->

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 999, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 41, Column 1: start tag was here
    <div id="placenta">

Visitor Analysis

Daily Visitor
  • 317.333 visits

In Page Analysis