thaivdox.com

เว็บโป๊ หนังx หนังโป๊ xxx ThaiVdox.com ...

Processing update domain...

Overview Info



  • Domain Name
    thaivdox.com
  • Favicon
  • Alexa Rank
    #1434668
  • Google Page Rank
    0
  • Ip Address
    192.241.204.138
  • Page Size
    53.1 KB
  • Images
    28 GIF, 16 JPG, 11 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 7 11 0 0

Website Meta Analysis



  • Title
    เว็บโป๊ หนังx หนังโป๊ xxx ThaiVdox.com
  • Meta Keyword
    หนังx, xxx, หนังโป๊, เว็บโป๊, porn, adult, 18+, หนังโป้
  • Meta Description
    เว็บโป๊ หนังx หนังโป๊ xxx ThaiVdox.com

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    192.241.204.138
  • Domain Age
    3 Months, 5 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 16 Aug 2013 07:58:48 GMT
  • server: Apache
  • x-powered-by: PHP/5.3.3
  • expires: Mon, 26 Jul 1997 05:00:00 GMT
  • cache-control: private
  • pragma: no-cache
  • last-modified: Fri, 16 Aug 2013 07:58:48 GMT
  • content-encoding: gzip
  • vary: Accept-Encoding
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for thaivdox.com

DNS Analysis


DNS servers
ns1qsy.name.com [184.172.60.176]
ns2fwz.name.com [98.124.246.1]
ns3fhx.name.com [208.43.116.43]
ns4qxz.name.com [107.21.243.34]


DNS Records

Answer records
thaivdox.com A 192.241.204.138 300s
thaivdox.com NS  ns1qsy.name.com 300s
thaivdox.com NS  ns3fhx.name.com 300s
thaivdox.com NS  ns2fwz.name.com 300s
thaivdox.com NS  ns4qxz.name.com 300s
thaivdox.com SOA
server: ns1qsy.name.com
email: [email protected]
serial: 1
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 300
300s

Authority records

Additional records
ns2fwz.name.com A 98.124.246.1 86400s
ns4qxz.name.com A 107.21.243.34 86400s
ns3fhx.name.com A 208.43.116.43 86400s
ns1qsy.name.com A 184.172.60.176 86400s

IP 192.241.204.138 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 90 Errors
  • 28 Warnings
Ratio Text/Html
  • 0.7129551227773074
Message Error
  • Error Line 23, Column 17: there is no attribute "property"
    	<meta property="fb:admins" content="100004368252726" />

    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 147, Column 47: required attribute "type" not specified
    	<div id="content_wrap"><!--Headers--><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 159, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 175, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

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

  • Warning Line 180, Column 164: cannot generate system identifier for general entity "width"
    …m/pages/Video-For-You/352868124803974&width=200&height=62&colorscheme=light&sh…

    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 180, Column 164: general entity "width" not defined and no default entity
    …m/pages/Video-For-You/352868124803974&width=200&height=62&colorscheme=light&sh…

    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 180, Column 169: reference not terminated by REFC delimiter
    …es/Video-For-You/352868124803974&width=200&height=62&colorscheme=light&show_fa…

    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 180, Column 169: reference to external entity in attribute value
    …es/Video-For-You/352868124803974&width=200&height=62&colorscheme=light&show_fa…

    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 180, Column 169: reference to entity "width" for which no system identifier could be generated
    …es/Video-For-You/352868124803974&width=200&height=62&colorscheme=light&show_fa…

    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 180, Column 163: entity was defined here
    …om/pages/Video-For-You/352868124803974&width=200&height=62&colorscheme=light&s…
  • Warning Line 180, Column 174: cannot generate system identifier for general entity "height"
    …deo-For-You/352868124803974&width=200&height=62&colorscheme=light&show_faces=f…

    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 180, Column 174: general entity "height" not defined and no default entity
    …deo-For-You/352868124803974&width=200&height=62&colorscheme=light&show_faces=f…

    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 180, Column 180: reference not terminated by REFC delimiter
    …r-You/352868124803974&width=200&height=62&colorscheme=light&show_faces=false&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 180, Column 180: reference to external entity in attribute value
    …r-You/352868124803974&width=200&height=62&colorscheme=light&show_faces=false&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 180, Column 180: reference to entity "height" for which no system identifier could be generated
    …r-You/352868124803974&width=200&height=62&colorscheme=light&show_faces=false&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 180, Column 173: entity was defined here
    …ideo-For-You/352868124803974&width=200&height=62&colorscheme=light&show_faces=…
  • Warning Line 180, Column 184: cannot generate system identifier for general entity "colorscheme"
    …u/352868124803974&width=200&height=62&colorscheme=light&show_faces=false&borde…

    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 180, Column 184: general entity "colorscheme" not defined and no default entity
    …u/352868124803974&width=200&height=62&colorscheme=light&show_faces=false&borde…

    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 180, Column 195: reference not terminated by REFC delimiter
    …803974&width=200&height=62&colorscheme=light&show_faces=false&border_color&str…

    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 180, Column 195: reference to external entity in attribute value
    …803974&width=200&height=62&colorscheme=light&show_faces=false&border_color&str…

    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 180, Column 195: reference to entity "colorscheme" for which no system identifier could be generated
    …803974&width=200&height=62&colorscheme=light&show_faces=false&border_color&str…

    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 180, Column 183: entity was defined here
    …ou/352868124803974&width=200&height=62&colorscheme=light&show_faces=false&bord…
  • Warning Line 180, Column 202: cannot generate system identifier for general entity "show_faces"
    …width=200&height=62&colorscheme=light&show_faces=false&border_color&stream=fal…

    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 180, Column 202: general entity "show_faces" not defined and no default entity
    …width=200&height=62&colorscheme=light&show_faces=false&border_color&stream=fal…

    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 180, Column 212: reference not terminated by REFC delimiter
    …height=62&colorscheme=light&show_faces=false&border_color&stream=false&header=…

    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 180, Column 212: reference to external entity in attribute value
    …height=62&colorscheme=light&show_faces=false&border_color&stream=false&header=…

    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 180, Column 212: reference to entity "show_faces" for which no system identifier could be generated
    …height=62&colorscheme=light&show_faces=false&border_color&stream=false&header=…

    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 180, Column 201: entity was defined here
    …&width=200&height=62&colorscheme=light&show_faces=false&border_color&stream=fa…
  • Warning Line 180, Column 219: cannot generate system identifier for general entity "border_color"
    …62&colorscheme=light&show_faces=false&border_color&stream=false&header=true" s…

    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 180, Column 219: general entity "border_color" not defined and no default entity
    …62&colorscheme=light&show_faces=false&border_color&stream=false&header=true" 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.

  • Warning Line 180, Column 231: reference not terminated by REFC delimiter
    …me=light&show_faces=false&border_color&stream=false&header=true" scrolling="no…

    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 180, Column 231: reference to external entity in attribute value
    …me=light&show_faces=false&border_color&stream=false&header=true" scrolling="no…

    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 180, Column 231: reference to entity "border_color" for which no system identifier could be generated
    …me=light&show_faces=false&border_color&stream=false&header=true" scrolling="no…

    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 180, Column 218: entity was defined here
    …=62&colorscheme=light&show_faces=false&border_color&stream=false&header=true" …
  • Warning Line 180, Column 232: cannot generate system identifier for general entity "stream"
    …e=light&show_faces=false&border_color&stream=false&header=true" scrolling="no"…

    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 180, Column 232: general entity "stream" not defined and no default entity
    …e=light&show_faces=false&border_color&stream=false&header=true" scrolling="no"…

    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 180, Column 238: reference not terminated by REFC delimiter
    …t&show_faces=false&border_color&stream=false&header=true" scrolling="no" frame…

    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 180, Column 238: reference to external entity in attribute value
    …t&show_faces=false&border_color&stream=false&header=true" scrolling="no" frame…

    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 180, Column 238: reference to entity "stream" for which no system identifier could be generated
    …t&show_faces=false&border_color&stream=false&header=true" scrolling="no" frame…

    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 180, Column 231: entity was defined here
    …me=light&show_faces=false&border_color&stream=false&header=true" scrolling="no…
  • Warning Line 180, Column 245: cannot generate system identifier for general entity "header"
    …faces=false&border_color&stream=false&header=true" scrolling="no" frameborder=…

    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 180, Column 245: general entity "header" not defined and no default entity
    …faces=false&border_color&stream=false&header=true" scrolling="no" frameborder=…

    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 180, Column 251: reference not terminated by REFC delimiter
    …false&border_color&stream=false&header=true" scrolling="no" frameborder="0" st…

    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 180, Column 251: reference to external entity in attribute value
    …false&border_color&stream=false&header=true" scrolling="no" frameborder="0" st…

    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 180, Column 251: reference to entity "header" for which no system identifier could be generated
    …false&border_color&stream=false&header=true" scrolling="no" frameborder="0" st…

    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 180, Column 244: entity was defined here
    …_faces=false&border_color&stream=false&header=true" scrolling="no" frameborder…
  • Error Line 180, Column 371: there is no attribute "allowTransparency"
    …rflow:hidden; width:200px; height:62px;" allowTransparency="true"></iframe></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 182, Column 46: character "+" is not allowed in the value of attribute "id"
    … class='social-while-block' id='google+1'><g:plusone size="tall"></g:plusone><…

    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 182, Column 66: there is no attribute "size"
    …ss='social-while-block' 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 182, Column 72: element "g:plusone" undefined
    …ss='social-while-block' 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 183, Column 124: there is no attribute "data-count"
    ….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.

  • Error Line 184, Column 40: ID "facebook" already defined
    			<div class='social-while-block' id='facebook'>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 180, Column 31: ID "facebook" first defined here
    			<p class='floatbutton' id='facebook'><iframe src="//www.facebook.com/plugins…
  • Error Line 185, Column 32: there is no attribute "data-send"
    <div class="fb-like" data-send="false" data-layout="box_count" data-width="50" …

    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 185, Column 52: there is no attribute "data-layout"
    …b-like" data-send="false" data-layout="box_count" data-width="50" data-show-fa…

    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 185, Column 75: there is no attribute "data-width"
    …e" data-layout="box_count" data-width="50" data-show-faces="false" data-font="…

    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 185, Column 96: there is no attribute "data-show-faces"
    …_count" data-width="50" data-show-faces="false" data-font="tahoma"></div></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 185, Column 114: there is no attribute "data-font"
    …_count" data-width="50" data-show-faces="false" data-font="tahoma"></div></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 189, Column 136: end tag for "img" omitted, but OMITTAG NO was specified
    …oTcwzYtI/UdrHELgPRHI/AAAAAAAAAFY/k2rUpElmhLo/s1600/contacts.gif" alt="ADS"></p>

    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 189, Column 19: start tag was here
    <p align="center"><img src="http://2.bp.blogspot.com/-Hl8oTcwzYtI/UdrHELgPRHI/A…
  • Error Line 193, Column 57: there is no attribute "onClick"
    …<span style="cursor: pointer" onClick="window.open ('http://seawzeed.com/?uid=…

    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 193, Column 243: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …AGdI/g7mChfBSPqo/s1600/seawzeednew.gif" border=0 alt="11/08/2013" /></span></p>
  • Error Line 195, Column 238: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …AH0/3WzUEVUk29o/s1600/total728x200.gif" border=0 alt="11/08/2013" /></span></p>
  • Error Line 203, Column 234: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …AAAAAAHk/QhUPaAkjxvE/s1600/650x200.gif" border=0 alt="11/08/2013" /></span></p>
  • Error Line 205, Column 239: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …AAAAAAAJA/VN659Xlzst4/s1600/728x90.gif" border=0 alt="20/10/2013" /></span></p>
  • Error Line 207, Column 267: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …nner-allonline88-size728x180-edit4.gif" border=0 alt="21/08/2013" /></span></p>
  • Error Line 209, Column 240: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/FIHm3qm7fQg/s1600/55555dadadadada.jpg" border=0 alt="28/08/2013" /></span></p>
  • Error Line 217, Column 257: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …J67DyWpMI/s1600/tt120x120.gif" border=0 alt="16/08/2013" /></span> <span style…
  • Error Line 217, Column 565: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …%B8%B3%E0%B8%99%E0%B8%B32.jpg" border=0 alt="20/08/2013" /></span> <span style…
  • Error Line 217, Column 817: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …15SWW5mdg/s1600/heedek120.gif" border=0 alt="25/08/2013" /></span> <a href="ht…
  • Error Line 217, Column 1085: required attribute "alt" not specified
    …AAADI/coxPHAaE-J0/s1600/120x120.gif" /></a> <a href="http://thaivdox.com/index…

    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 217, Column 1330: required attribute "alt" not specified
    …AAADI/coxPHAaE-J0/s1600/120x120.gif" /></a> <span style="cursor: pointer" onCl…

    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 217, Column 1541: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …AAAAAAAAAD0/uXugWz3Ci3U/s1600/vdox.gif" border=0 alt="12/10/2013" /></span></p>
  • Error Line 219, Column 258: required attribute "alt" not specified
    …AAADI/coxPHAaE-J0/s1600/120x120.gif" /></a> <a href="http://thaivdox.com/index…

    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 219, Column 503: required attribute "alt" not specified
    …AAADI/coxPHAaE-J0/s1600/120x120.gif" /></a> <a href="http://thaivdox.com/index…

    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 219, Column 748: required attribute "alt" not specified
    …AAADI/coxPHAaE-J0/s1600/120x120.gif" /></a> <a href="http://thaivdox.com/index…

    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 219, Column 993: required attribute "alt" not specified
    …AAADI/coxPHAaE-J0/s1600/120x120.gif" /></a> <a href="http://thaivdox.com/index…

    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 219, Column 1238: required attribute "alt" not specified
    …AAADI/coxPHAaE-J0/s1600/120x120.gif" /></a> <span style="cursor: pointer" onCl…

    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 219, Column 1459: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …AAAADw/8WObyMzHYxo/s1600/siamclipx.gif" border=0 alt="14/11/2013" /></span></p>
  • Error Line 221, Column 245: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …8OG2Yc/s1600/bbmaxxthai.com800x300.gif" border=0 alt="21/08/2013" /></span></p>
  • Error Line 226, Column 42: there is no attribute "alt"
    …href="http://www.morevisits.info" alt="free backlink tool " target="_blank"><i…

    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 226, Column 321: required attribute "alt" not specified
    …A3" title="Free backlink" border="0" /></a><noscript><a href="http://www.meteo…

    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 226, Column 335: document type does not allow element "noscript" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …e backlink" border="0" /></a><noscript><a href="http://www.meteoa12jours.net/"…

    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 227, Column 313: required attribute "alt" not specified
    …E8" title="Free backlink" border="0" /></a><noscript><a href="http://www.dnsbl…

    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 227, Column 327: document type does not allow element "noscript" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …e backlink" border="0" /></a><noscript><a href="http://www.dnsblcheck.org/" al…

    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 228, Column 303: required attribute "alt" not specified
    …CF" title="Free backlink" border="0" /></a><noscript><a href="http://meteo123.…

    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 228, Column 317: document type does not allow element "noscript" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …e backlink" border="0" /></a><noscript><a href="http://meteo123.net/meteo-regi…

    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 229, Column 312: required attribute "alt" not specified
    …75" title="Free backlink" border="0" /></a><noscript><a href="http://meteo123.…

    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 229, Column 326: document type does not allow element "noscript" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …e backlink" border="0" /></a><noscript><a href="http://meteo123.net/meteo-11-j…

    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 230, Column 316: required attribute "alt" not specified
    …42" title="Free backlink" border="0" /></a><noscript><a href="http://meteo123.…

    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 230, Column 330: document type does not allow element "noscript" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …e backlink" border="0" /></a><noscript><a href="http://meteo123.net/meteo-regi…

    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 581, Column 190: end tag for "img" omitted, but OMITTAG NO was specified
    …-16.png" alt="มรกต เพิ่มพูลทรัพย์"></a> <a href="https://www.facebook.com/page…

    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 581, Column 89: start tag was here
    …m/111034754120272856429" rel="author"><img src="http://www.google.com/images/i…
  • Error Line 581, Column 408: end tag for "img" omitted, but OMITTAG NO was specified
    …2253_750145931.png" alt="Facebook"></a> <script type="text/javascript" languag…

    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 581, Column 300: start tag was here
    … title="Video For You" rel="nofollow"><img src="http://dragon.ak.fbcdn.net/cfs…
  • Error Line 583, Column 12: there is no attribute "src"
    <embed src="http://s10.histats.com/138.swf"  flashvars="jver=1&acsid=2333294&do…

    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 583, Column 56: there is no attribute "flashvars"
    …//s10.histats.com/138.swf"  flashvars="jver=1&acsid=2333294&domi=4"  quality="…

    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 583, Column 64: cannot generate system identifier for general entity "acsid"
    …stats.com/138.swf"  flashvars="jver=1&acsid=2333294&domi=4"  quality="high"  w…

    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 583, Column 64: general entity "acsid" not defined and no default entity
    …stats.com/138.swf"  flashvars="jver=1&acsid=2333294&domi=4"  quality="high"  w…

    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 583, Column 69: reference not terminated by REFC delimiter
    ….com/138.swf"  flashvars="jver=1&acsid=2333294&domi=4"  quality="high"  width=…

    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 583, Column 69: reference to external entity in attribute value
    ….com/138.swf"  flashvars="jver=1&acsid=2333294&domi=4"  quality="high"  width=…

    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 583, Column 69: reference to entity "acsid" for which no system identifier could be generated
    ….com/138.swf"  flashvars="jver=1&acsid=2333294&domi=4"  quality="high"  width=…

    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 583, Column 63: entity was defined here
    …istats.com/138.swf"  flashvars="jver=1&acsid=2333294&domi=4"  quality="high"  …
  • Warning Line 583, Column 78: cannot generate system identifier for general entity "domi"
    …swf"  flashvars="jver=1&acsid=2333294&domi=4"  quality="high"  width="112" hei…

    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 583, Column 78: general entity "domi" not defined and no default entity
    …swf"  flashvars="jver=1&acsid=2333294&domi=4"  quality="high"  width="112" hei…

    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 583, Column 82: reference not terminated by REFC delimiter
    …  flashvars="jver=1&acsid=2333294&domi=4"  quality="high"  width="112" height=…

    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 583, Column 82: reference to external entity in attribute value
    …  flashvars="jver=1&acsid=2333294&domi=4"  quality="high"  width="112" height=…

    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 583, Column 82: reference to entity "domi" for which no system identifier could be generated
    …  flashvars="jver=1&acsid=2333294&domi=4"  quality="high"  width="112" height=…

    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 583, Column 77: entity was defined here
    ….swf"  flashvars="jver=1&acsid=2333294&domi=4"  quality="high"  width="112" he…
  • Error Line 583, Column 95: there is no attribute "quality"
    …jver=1&acsid=2333294&domi=4"  quality="high"  width="112" height="33" name="13…

    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 583, Column 109: there is no attribute "width"
    …333294&domi=4"  quality="high"  width="112" height="33" name="138.swf"  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 583, Column 122: there is no attribute "height"
    …"  quality="high"  width="112" height="33" name="138.swf"  align="middle" type…

    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 583, Column 132: there is no attribute "name"
    …="high"  width="112" height="33" name="138.swf"  align="middle" type="applicat…

    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 583, Column 149: there is no attribute "align"
    …12" height="33" name="138.swf"  align="middle" type="application/x-shockwave-f…

    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 583, Column 163: there is no attribute "type"
    …" name="138.swf"  align="middle" type="application/x-shockwave-flash" pluginsp…

    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 583, Column 207: there is no attribute "pluginspage"
    …cation/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 583, Column 259: there is no attribute "wmode"
    …nspage="http://www.macromedia.com/go/getflashplayer" wmode="transparent" /></a>

    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 583, Column 274: element "embed" undefined
    …nspage="http://www.macromedia.com/go/getflashplayer" wmode="transparent" /></a>

    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 584, Column 53: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?2333294&101" alt="frontpage 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 584, Column 98: end tag for "img" omitted, but OMITTAG NO was specified
    …sstatic1.histats.com/0.gif?2333294&101" alt="frontpage hit counter" border="0">

    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 584, Column 1: start tag was here
    <img  src="http://sstatic1.histats.com/0.gif?2333294&101" alt="frontpage hit co…
  • Error Line 589, Column 4: character data is not allowed here
    			Copyright © 2012 - 2013 By <a href="http://thaivdox.com" title="Thaivdox.com…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 589, Column 81: document type does not allow element "a" here; assuming missing "li" start-tag
    …http://thaivdox.com" title="Thaivdox.com">Thaivdox.com</a> All Rights Reserved.
  • Error Line 590, Column 25: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li class="copyright">

    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 595, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a rel="nofollow" href="http://www.jpr62.com/theme/" target="_blank" cla…

    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 596, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a rel="nofollow" id="button_xhtml" href="http://validator.w3.org/check?…

    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 597, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a rel="nofollow" id="button_rss" href="http://thaivdox.com/index.php?PH…

    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 598, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a rel="nofollow" id="button_wap2" href="http://thaivdox.com/index.php?P…

    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 599, Column 20: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li class="last"><a rel="nofollow" href="http://thaivdox.com/index.php?PHPSE…

    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 600, Column 7: 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 589, Column 31: start tag was here
    			Copyright © 2012 - 2013 By <a href="http://thaivdox.com" title="Thaivdox.com…
  • Error Line 604, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body></html>

    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 39, Column 2: start tag was here
    	<div id="ob1">
  • Error Line 604, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body></html>

    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 38, Column 1: start tag was here
    <div class="content_wrap" id="mainframe" style="width: 1000px">

Visitor Analysis

Daily Visitor
  • 1.283 visits

In Page Analysis