vdo9x.com

vdo9x.com has Alexa Rank 30.664 and Google Page Rank is 3

Display Widget for this domain on your website. Click Here
This data was last updated from 30-07-2013 01:12:09  (update).

Overview Info

  • Domain Name
    vdo9x.com
  • Favicon
  • Alexa Rank
    #30664
  • Google Page Rank
    PR 3
  • Ip Address
    199.168.97.106
  • Page Size
    56.3 KB
  • Images
    29 GIF, 86 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 15 1 1 1 0

Technical Analysis



  • Webserver
    nginx/1.3.11
  • Ip Address
    199.168.97.106
  • Domain Age
    1 Years, 6 Months, 24 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.3.11
  • date: Tue, 30 Jul 2013 21:17:03 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-powered-by: PHP/5.2.17
  • pragma: no-cache
  • cache-control: private
  • expires: Mon, 26 Jul 1997 05:00:00 GMT
  • last-modified: Tue, 30 Jul 2013 21:17:03 GMT
  • content-encoding: gzip
  • vary: Accept-Encoding
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for vdo9x.com

DNS Analysis


DNS servers
paul.ns.cloudflare.com [173.245.59.135]
gail.ns.cloudflare.com [173.245.58.116]


DNS Records

Answer records
vdo9x.com A 141.101.117.44 300s
vdo9x.com A 141.101.116.44 300s
vdo9x.com NS  paul.ns.cloudflare.com 86400s
vdo9x.com NS  gail.ns.cloudflare.com 86400s
vdo9x.com SOA
server: gail.ns.cloudflare.com
email: dns@cloudflare.com
serial: 2013020219
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s
vdo9x.com TXT v=spf1 a mx ip4:63.141.238.178 ~all 300s
vdo9x.com MX
preference: 10
exchange: mail.vdo9x.com
300s

Authority records

Additional records
mail.vdo9x.com A 63.141.238.178 300s

IP 199.168.97.106 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 14 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.5934542176611309
Message Error
  • Error Line 248, Column 63: required attribute "type" not specified
    <script src="http://connect.facebook.net/en_US/all.js#xfbml=1"></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 254, Column 56: there is no attribute "layout"
    …button' id='facebook'><fb:like layout="box_count" show_faces="false"></fb:like…

    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 254, Column 79: there is no attribute "show_faces"
    …' id='facebook'><fb:like layout="box_count" show_faces="false"></fb:like></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 254, Column 86: element "fb:like" undefined
    …' id='facebook'><fb:like layout="box_count" show_faces="false"></fb:like></div>

    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 255, Column 36: character "+" is not allowed in the value of attribute "id"
    <div class='floatbutton' id='google+1'><g:plusone size="tall"></g:plusone></div>

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 255, Column 56: there is no attribute "size"
    <div class='floatbutton' id='google+1'><g:plusone size="tall"></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 255, Column 62: element "g:plusone" undefined
    <div class='floatbutton' id='google+1'><g:plusone size="tall"></g:plusone></div>

    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 256, Column 114: there is no attribute "data-count"
    …r.com/share" class="twitter-share-button" data-count="vertical">Tweet</a></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.

  • Warning Line 274, Column 111: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?1874639&101" alt="web site 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 274, Column 158: end tag for "img" omitted, but OMITTAG NO was specified
    …ts.com/0.gif?1874639&101" alt="web site 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 274, Column 60: start tag was here
    …tp://www.histats.com" target="_blank"><img src="http://sstatic1.histats.com/0.…
  • Warning Line 359, Column 28: character "&" is the first character of a delimiter but occurred as data
    var ieNOTopera=document.all&&navigator.userAgent.indexOf("Opera")==-1

    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 359, Column 30: cannot generate system identifier for general entity "navigator.userAgent.indexOf"
    var ieNOTopera=document.all&&navigator.userAgent.indexOf("Opera")==-1

    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 359, Column 30: general entity "navigator.userAgent.indexOf" not defined and no default entity
    var ieNOTopera=document.all&&navigator.userAgent.indexOf("Opera")==-1

    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 359, Column 57: reference not terminated by REFC delimiter
    var ieNOTopera=document.all&&navigator.userAgent.indexOf("Opera")==-1

    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.

  • Error Line 359, Column 57: reference to entity "navigator.userAgent.indexOf" for which no system identifier could be generated
    var ieNOTopera=document.all&&navigator.userAgent.indexOf("Opera")==-1

    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 359, Column 29: entity was defined here
    var ieNOTopera=document.all&&navigator.userAgent.indexOf("Opera")==-1
  • Warning Line 378, Column 29: character "&" is the first character of a delimiter but occurred as data
    return (document.compatMode && document.compatMode!="BackCompat")? document.doc…

    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 378, Column 30: character "&" is the first character of a delimiter but occurred as data
    return (document.compatMode && document.compatMode!="BackCompat")? document.doc…

    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 466, Column 12: there is no attribute "onClick"
    <a onClick="this.parentNode.parentNode.parentNode.removeChild(this.parentNode.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.

  • Warning Line 514, Column 42: character "&" is the first character of a delimiter but occurred as data
    …             document.documentElement && document.documentElement.clientWidth …

    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 514, Column 43: character "&" is the first character of a delimiter but occurred as data
    …             document.documentElement && document.documentElement.clientWidth ?

    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 516, Column 62: character "&" is the first character of a delimiter but occurred as data
    … pageYOffset : document.documentElement && document.documentElement.scrollTop ?

    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 516, Column 63: character "&" is the first character of a delimiter but occurred as data
    … pageYOffset : document.documentElement && document.documentElement.scrollTop ?

    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 518, Column 23: character "<" is the first character of a delimiter but occurred as data
                if(this.sy<0)

    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 519, Column 67: character "&" is the first character of a delimiter but occurred as data
    …nnerHeight : document.documentElement && document.documentElement.clientHeight…

    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 519, Column 68: character "&" is the first character of a delimiter but occurred as data
    …nerHeight : document.documentElement && document.documentElement.clientHeight …

    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.

Visitor Analysis

Daily Visitor
  • 1.633 visits

In Page Analysis