xnxx.sh

Home XNX.TV Redtube Japan xnxx Home Teen Anal Asian Big Tits Hardcore Milf XNXX New Videos Beautiful woman reaches her orgasm outdoors ... 1 hour ago  Loading ... 12 views Dirty Fucking Russian ...

This data was last updated from 04-08-2014 05:33:08  (update).

Overview Info



  • Domain Name
    xnxx.sh
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    1
  • Ip Address
    104.28.3.65
  • Page Size
    78.2 KB
  • Images
    120 GIF, 20 JPG, 45 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 3 0 0 5 0

Website Meta Analysis



  • Title
    XNXX, XNXX.COM, XNXXX, XNXXX, XXNX XNXX, XNXX.COM, XNXXX, XNXXX, XXNX
  • Meta Keyword
  • Meta Description
    Home XNX.TV Redtube Japan xnxx Home Teen Anal Asian Big Tits Hardcore Milf XNXX New Videos Beautiful woman reaches her orgasm outdoors ... 1 hour ago  Loading ... 12 views Dirty Fucking Russian MILF xnxx 1 hour ago  Loading ... 11 views Nikki ...

Technical Analysis



  • Webserver
    cloudflare-nginx
  • Ip Address
    104.28.3.65
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from xnxx.sh.

HTML Analysis

  • date: Mon, 04 Aug 2014 05:33:07 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-powered-by: PHP/5.3.28
  • x-pingback: http://xnxx.sh/xmlrpc.php
  • server: cloudflare-nginx
  • cf-ray: 154860d5849f09a0-ORD
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for xnxx.sh

IP 104.28.3.65 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 66 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.8527745188587404
Message Error
  • Error Line 2, Column 64: there is no attribute "prefix"
    …lns="http://www.w3.org/1999/xhtml" lang="en-US" prefix="og: http://ogp.me/ns#">

    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 5, Column 84: end tag for "meta" omitted, but OMITTAG NO was specified
    …a name="juicyads-site-verification" content="6e3d8867c7f6ac6f4695bfeccde53b9a">

    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 name="juicyads-site-verification" content="6e3d8867c7f6ac6f4695bfeccde53b…
  • Error Line 18, Column 16: there is no attribute "property"
    <meta property="og:locale" content="en_US"/>

    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 69, Column 16: there is no attribute "border"
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=924 height=25…

    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 69, 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=924 height=25…
  • Error Line 69, 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=924 height=25…
  • Error Line 69, 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=924 height=258 scr…
  • Error Line 69, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=924 height=258 scrolling=no allo…
  • Error Line 69, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=924 height=258 scrolling=no allowtranspa…
  • Error Line 69, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=924 height=258 scrolling=no allowtransparency=true …
  • Error Line 69, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=924 height=258 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 69, Column 113: there is no attribute "allowtransparency"
    …ht=258 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 69, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=258 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 69, Column 122: 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 69, Column 128: 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 69, Column 184: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=238097></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 81, Column 202: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 90, Column 62: there is no attribute "data-nonce"
    …1978" class="post-ratings" data-nonce="2093614e11"><img id="rating_11978_1" sr…

    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 97, Column 168: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 113, Column 204: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 129, Column 144: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 145, Column 164: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 161, Column 147: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 177, Column 162: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 193, Column 194: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 209, Column 208: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 225, Column 190: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 241, Column 188: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 257, Column 194: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 273, Column 210: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 289, Column 132: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 305, Column 186: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 321, Column 206: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 337, Column 176: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 353, Column 170: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 369, Column 168: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 385, Column 175: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"overlay"></span><div class="featured"><img src="http://xnxx.sh/wp-content/the…

    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 428, 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=168 height=60…
  • Error Line 428, 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=168 height=60…
  • Error Line 428, 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=168 height=608 scr…
  • Error Line 428, Column 59: 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 428, Column 67: 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 428, Column 78: 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 428, Column 92: 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 428, Column 113: 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 428, Column 122: 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 428, Column 128: 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 428, Column 184: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=238098></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 489, 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=924 height=25…
  • Error Line 489, 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=924 height=25…
  • Error Line 489, 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=924 height=258 scr…
  • Error Line 489, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=924 height=258 scrolling=no allo…
  • Error Line 489, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=924 height=258 scrolling=no allowtranspa…
  • Error Line 489, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=924 height=258 scrolling=no allowtransparency=true …
  • Error Line 489, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=924 height=258 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 489, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=258 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 489, Column 122: 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 489, Column 128: 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 489, Column 184: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=238097></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 494, Column 74: required attribute "type" not specified
    …ipt src="//ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js"></script>

    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 549, Column 108: end tag for "img" omitted, but OMITTAG NO was specified
    …xx.sh/wp-content/themes/sam-movie/images/footer/facebook.png" alt="#"></a></li>

    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 549, Column 16: start tag was here
    <li><a href=""><img src="http://xnxx.sh/wp-content/themes/sam-movie/images/foot…
  • Error Line 550, Column 107: end tag for "img" omitted, but OMITTAG NO was specified
    …nxx.sh/wp-content/themes/sam-movie/images/footer/twitter.png" alt="#"></a></li>

    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 550, Column 16: start tag was here
    <li><a href=""><img src="http://xnxx.sh/wp-content/themes/sam-movie/images/foot…
  • Error Line 551, Column 107: end tag for "img" omitted, but OMITTAG NO was specified
    …nxx.sh/wp-content/themes/sam-movie/images/footer/youtube.png" alt="#"></a></li>

    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 551, Column 16: start tag was here
    <li><a href=""><img src="http://xnxx.sh/wp-content/themes/sam-movie/images/foot…
  • Error Line 552, Column 122: end tag for "img" omitted, but OMITTAG NO was specified
    …://xnxx.sh/wp-content/themes/sam-movie/images/footer/rss.png" alt="#"></a></li>

    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 552, Column 35: start tag was here
    <li><a href="http://xnxx.sh/feed"><img src="http://xnxx.sh/wp-content/themes/sa…
  • Error Line 560, Column 7: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><h1> XNXX, XNXX.COM, WWW.XNXXX.COM, XNX, XXNX, XNX.COM, XXX.COM, XXX, SEX, F…

    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>").

  • Warning Line 579, Column 111: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?2403759&101" alt="free web hit counter" border=…

    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 579, Column 158: end tag for "img" omitted, but OMITTAG NO was specified
    …ts.com/0.gif?2403759&101" alt="free web hit counter" border="0"></a></noscript>

    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 579, Column 60: start tag was here
    …tp://www.histats.com" target="_blank"><img src="http://sstatic1.histats.com/0.…

Visitor Analysis

Daily Visitor
  • 58 visits

In Page Analysis