phimp.net

phimp.net has Alexa Rank 96.018 and Google Page Rank is 1

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    phimp.net
  • Favicon
  • Alexa Rank
    #96018
  • Google Page Rank
    PR 1
  • Ip Address
    123.30.187.197
  • Page Size
    49.8 KB
  • Images
    1 GIF, 23 JPG, 2 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 8 27 0 0 0

Website Meta Analysis



  • Meta Keyword

Technical Analysis



  • Webserver
  • Ip Address
    123.30.187.197
  • Domain Age
    9 Months, 29 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from phimp.net.

HTML Analysis

  • date: Mon, 22 Jul 2013 02:03:03 GMT
  • x-powered-by: PHP/5.2.17
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • expires: Tue, 31 Dec 1980 00:00:01 GMT
  • cache-control: private
  • pragma: private
  • content-length: 13669
  • content-type: text/html; charset=UTF-8
  • connection: close
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for phimp.net

DNS Analysis


DNS servers
ns17.domaincontrol.com [216.69.185.9]
ns18.domaincontrol.com [208.109.255.9]


DNS Records

Answer records
phimp.net A 123.30.187.197 3600s
phimp.net MX
preference: 0
exchange: smtp.secureserver.net
3600s
phimp.net MX
preference: 10
exchange: mailstore1.secureserver.net
3600s
phimp.net NS  ns17.domaincontrol.com 3600s
phimp.net NS  ns18.domaincontrol.com 3600s
phimp.net SOA
server: ns17.domaincontrol.com
email: dns@jomax.net
serial: 2012122400
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records

IP 123.30.187.197 Analysis

  • Country Code
    VN
  • Country Code3
    VNM
  • Country Name
    Vietnam
  • City
    Hanoi
  • Continent Code
    AS
  • Latitude
    21.0333
  • Longitude
    105.85
  • % [whois.apnic.net node-2]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 123.30.0.0 - 123.31.255.255
    netname: VDC-NET
    country: vn
    descr: VietNam Data Communication Company (VDC)
    admin-c: VIG1-AP
    tech-c: VIG1-AP
    status: ALLOCATED NON-PORTABLE
    changed: hm-changed@vnnic.net.vn 20090325
    mnt-by: MAINT-VN-VNPT
    source: APNIC

    route: 123.30.128.0/18
    descr: VietNam Post and Telecom Corporation (VNPT)
    descr: VNPT-AS-AP
    country: VN
    origin: AS7643
    remarks: mailto: noc@vnn.vn
    notify: hm-changed@vnnic.net.vn
    mnt-by: MAINT-VN-VNPT
    changed: hm-changed@vnnic.net.vn 20100121
    source: APNIC

    role: VDC IPADMIN GROUP
    address: Internet Building, Block II, Thang Long Inter Village
    address: Nguyen Phong Sac str, Cau Giay Dist, Ha Noi
    country: VN
    phone: +84-912-800008
    fax-no: +84-4-9430427
    e-mail: hathm@vdc.com.vn
    remarks: send spam reports to abuse@vdc.com.vn
    remarks: and abuse reports to abuse@vnn.vn
    admin-c: THMH1-AP
    tech-c: THMH1-AP
    nic-hdl: VIG1-AP
    notify: hm-changed@vnnic.net.vn
    mnt-by: MAINT-VN-VNPT
    changed: hm-changed@vnnic.net.vn 20090325
    source: APNIC
    changed: hm-changed@apnic.net 20111114


Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 20 Errors
  • 14 Warnings
Ratio Text/Html
  • 0.6119385435447205
Message Error
  • Error Line 4, Column 20: there is no attribute "property"
        <meta property="fb:app_id" content="374105875994454" />

    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 141, Column 336: end tag for "input" omitted, but OMITTAG NO was specified
    …is.value = &quot;Tìm kiếm&quot;;}" id="keyword" class="default" name="keyword">

    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 141, Column 100: start tag was here
    …earch()" method="get">                <input type="text" value="Tìm kiếm" onfo…
  • Error Line 163, Column 181: end tag for "param" omitted, but OMITTAG NO was specified
    …em.com/banner/ldk_980x90.swf"><param name="wmode" value="transparent"></object>

    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 163, Column 133: start tag was here
    …ithienkiem.com/banner/ldk_980x90.swf"><param name="wmode" value="transparent">…
  • Warning Line 205, Column 126: cannot generate system identifier for general entity "w"
    …?src=uploads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ…

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

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

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

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

  • Error Line 205, Column 126: general entity "w" not defined and no default entity
    …?src=uploads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ…

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

  • Warning Line 205, Column 127: reference not terminated by REFC delimiter
    …src=uploads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ …

    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 205, Column 127: reference to external entity in attribute value
    …src=uploads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ …

    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 205, Column 127: reference to entity "w" for which no system identifier could be generated
    …src=uploads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ …

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

  • Info Line 205, Column 125: entity was defined here
    …p?src=uploads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - N…
  • Warning Line 205, Column 132: cannot generate system identifier for general entity "zc"
    …ploads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ Hoàng…

    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 205, Column 132: general entity "zc" not defined and no default entity
    …ploads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ Hoàng…

    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 205, Column 134: reference not terminated by REFC delimiter
    …oads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ Hoàng T…

    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 205, Column 134: reference to external entity in attribute value
    …oads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ Hoàng T…

    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 205, Column 134: reference to entity "zc" for which no system identifier could be generated
    …oads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ Hoàng T…

    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 205, Column 131: entity was defined here
    …uploads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ Hoàn…
  • Warning Line 606, Column 127: reference not terminated by REFC delimiter
    …src=uploads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ …

    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 606, Column 127: reference to external entity in attribute value
    …src=uploads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ …

    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 606, Column 127: reference to entity "w" for which no system identifier could be generated
    …src=uploads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ …

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

  • Info Line 205, Column 125: entity was defined here
    …p?src=uploads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - N…
  • Warning Line 606, Column 134: reference not terminated by REFC delimiter
    …oads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ Hoàng T…

    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 606, Column 134: reference to external entity in attribute value
    …oads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ Hoàng T…

    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 606, Column 134: reference to entity "zc" for which no system identifier could be generated
    …oads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ Hoàng T…

    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 205, Column 131: entity was defined here
    …uploads/2012/08/May-Queen-04.jpg&w=150&zc=1" alt="Xem phim May Queen - Nữ Hoàn…
  • Error Line 690, Column 41: there is no attribute "size"
    …                      <g:plusone size="medium" expr:href="http://phimp.net"></…

    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 690, Column 60: there is no attribute "expr:href"
    …             <g:plusone size="medium" expr:href="http://phimp.net"></g:plusone>

    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 690, Column 78: element "g:plusone" undefined
    …             <g:plusone size="medium" expr:href="http://phimp.net"></g:plusone>

    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 693, Column 371: there is no attribute "allowTransparency"
    … overflow:hidden; width:450px; height:21px;" allowTransparency="true"></iframe>

    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 698, Column 44: there is no attribute "data-href"
    …   <div class="fb-like-box" data-href="https://www.facebook.com/phimp.net" dat…

    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 698, Column 92: there is no attribute "data-width"
    …ww.facebook.com/phimp.net" data-width="292" data-colorscheme="dark" data-show-…

    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 698, Column 115: there is no attribute "data-colorscheme"
    …et" data-width="292" data-colorscheme="dark" data-show-faces="false" data-stre…

    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 698, Column 138: there is no attribute "data-show-faces"
    …ta-colorscheme="dark" data-show-faces="false" data-stream="false" data-header=…

    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 698, Column 158: there is no attribute "data-stream"
    …me="dark" data-show-faces="false" data-stream="false" data-header="true"></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 698, Column 178: there is no attribute "data-header"
    …me="dark" data-show-faces="false" data-stream="false" data-header="true"></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 706, Column 148: required attribute "alt" not specified
    …blank"><img width="100%" border="0" src="http://phimp.net/images/adv1.gif"></a>

    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 706, Column 152: end tag for "img" omitted, but OMITTAG NO was specified
    …blank"><img width="100%" border="0" src="http://phimp.net/images/adv1.gif"></a>

    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 706, Column 81: start tag was here
    …//phimp.net/adv/ads1" target="_blank"><img width="100%" border="0" src="http:/…
  • Error Line 877, Column 33: required attribute "type" not specified
                <script id="_waui8o">var _wau = _wau || []; _wau.push(["small", "9z…

    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 918, Column 54: required attribute "type" not specified
    <script src="http://adbroker.zing.vn/res1/crystal.js"></script>

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

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

  • Warning Line 919, Column 71: cannot generate system identifier for general entity "callback"
    …er.zing.vn/lview?loc=_adb_22_10003003&callback=crystal2.addStaticSlot"></scrip…

    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 919, Column 71: general entity "callback" not defined and no default entity
    …er.zing.vn/lview?loc=_adb_22_10003003&callback=crystal2.addStaticSlot"></scrip…

    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 919, Column 79: reference not terminated by REFC delimiter
    …r.zing.vn/lview?loc=_adb_22_10003003&callback=crystal2.addStaticSlot"></script>

    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 919, Column 79: reference to external entity in attribute value
    …r.zing.vn/lview?loc=_adb_22_10003003&callback=crystal2.addStaticSlot"></script>

    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 919, Column 79: reference to entity "callback" for which no system identifier could be generated
    …r.zing.vn/lview?loc=_adb_22_10003003&callback=crystal2.addStaticSlot"></script>

    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 919, Column 70: entity was defined here
    …ker.zing.vn/lview?loc=_adb_22_10003003&callback=crystal2.addStaticSlot"></scri…
  • Error Line 919, Column 103: required attribute "type" not specified
    …r.zing.vn/lview?loc=_adb_22_10003003&callback=crystal2.addStaticSlot"></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 920, Column 8: required attribute "type" not specified
    <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>.

  • Warning Line 931, Column 17: character "<" is the first character of a delimiter but occurred as data
    	if(windowWidth < 1000){

    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 940, Column 34: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <div id="ad_right"><iframe align=center width="130px" height="600px" frameborde…
  • Error Line 940, Column 34: value of attribute "align" cannot be "center"; must be one of "top", "middle", "bottom", "left", "right"
    <div id="ad_right"><iframe align=center width="130px" height="600px" frameborde…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 940, Column 126: there is no attribute "vspace"
    …rginwidth="0" marginheight="0" vspace="0" hspace="0" allowtransparency="true" …

    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 940, Column 137: there is no attribute "hspace"
    …0" marginheight="0" vspace="0" hspace="0" allowtransparency="true" scrolling="…

    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 940, Column 159: there is no attribute "allowtransparency"
    …pace="0" hspace="0" allowtransparency="true" scrolling="no" src="http://ad.tha…

    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.

Visitor Analysis

Daily Visitor
  • 362 visits

In Page Analysis