Xem phim online - Website xem phim online, trực tuyến nhanh nhất trên các mạng fpt, vnpt và viettel. Download và cập nhật nhiều bộ phim hay mới 3D, HD, DVD... ...

bomtan.org
  • Domain Name
    bomtan.org
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #106762
  • Page Size
    153.9 KB
  • Ip Address
    123.30.129.189
  • Heading
    H1: 1, H2: 14, H3: 35, H4: 40, H5: 0, H6: 0
  • Images
    0 GIF, 81 JPG, 121 PNG

Website Meta Analysis

  • Title
    Xem phim | Phim online | Phim | Trực tuyến | phim nhanh
  • Meta Keyword
    ,xem, phim, online, trực tuyến, nhanh, mạng, vnpt, fpt, viettel, hay, 3d, hd, dvd, download
  • Meta Description
    Xem phim online - Website xem phim online, trực tuyến nhanh nhất trên các mạng fpt, vnpt và viettel. Download và cập nhật nhiều bộ phim hay mới 3D, HD, DVD...

Technical Analysis

  • Webserver
    Apache/2.2.23 (CentOS)
  • Ip Address
    123.30.129.189
  • Domain Age
    11 Months, 26 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from bomtan.org.

HTML Analysis

  • date: Sat, 02 Mar 2013 13:37:23 GMT
  • server: Apache/2.2.23 (CentOS)
  • x-powered-by: PHP/5.2.17
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Access to .ORG WHOIS information is provided to assist persons in
determining the contents of a domain name registration record in the
Public Interest Registry registry database. The data in this record is provided by
Public Interest Registry for informational purposes only, and Public Interest Registry does not
guarantee its accuracy. This service is intended only for query-based
access. You agree that you will use this data only for lawful purposes
and that, under no circumstances will you use this data to: (a) allow,
enable, or otherwise support the transmission by e-mail, telephone, or
facsimile of mass unsolicited, commercial advertising or solicitations
to entities other than the data recipient's own existing customers; or
(b) enable high volume, automated, electronic processes that send
queries or data to the systems of Registry Operator, a Registrar, or
Afilias except as reasonably necessary to register domain names or
modify existing registrations. All rights reserved. Public Interest Registry reserves
the right to modify these terms at any time. By submitting this query,
you agree to abide by this policy.

Domain ID:D164965442-LROR
Domain Name:BOMTAN.ORG
Created On:11-Mar-2012 05:05:24 UTC
Last Updated On:08-Dec-2012 03:28:29 UTC
Expiration Date:11-Mar-2013 05:05:24 UTC
Sponsoring Registrar:OnlineNIC Inc. (R64-LROR)
Status:OK
Registrant ID:oln120834247
Registrant Name:Dang Dinh Cuong
Registrant Organization:Dang Dinh Cuong
Registrant Street1:Tu Son - Bac Ninh
Registrant Street2:Tu Son - Bac Ninh
Registrant Street3:
Registrant City:Bac Ninh
Registrant State/Province:Bac Ninh
Registrant Postal Code:84
Registrant Country:VN
Registrant Phone:+84.1674524368
Registrant Phone Ext.:
Registrant FAX:+84.1674524368
Registrant FAX Ext.:
Registrant Email: email
Admin ID:oln120834256
Admin Name:Dang Dinh Cuong
Admin Organization:Dang Dinh Cuong
Admin Street1:Tu Son - Bac Ninh
Admin Street2:Tu Son - Bac Ninh
Admin Street3:
Admin City:Bac Ninh
Admin State/Province:Bac Ninh
Admin Postal Code:84
Admin Country:VN
Admin Phone:+84.1674524368
Admin Phone Ext.:
Admin FAX:+84.1674524368
Admin FAX Ext.:
Admin Email: email
Tech ID:oln120834262
Tech Name:Dang Dinh Cuong
Tech Organization:Dang Dinh Cuong
Tech Street1:Tu Son - Bac Ninh
Tech Street2:Tu Son - Bac Ninh
Tech Street3:
Tech City:Bac Ninh
Tech State/Province:Bac Ninh
Tech Postal Code:84
Tech Country:VN
Tech Phone:+84.1674524368
Tech Phone Ext.:
Tech FAX:+84.1674524368
Tech FAX Ext.:
Tech Email: email
Name Server:NS1.DIGIPOWERDNS.COM
Name Server:NS2.DIGIPOWERDNS.COM
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
DNSSEC:Unsigned

IP 123.30.129.189 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-1]
    % 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


In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 60 Errors
  • 19 Warnings
Ratio Text/Html
  • 0.5898084889083424
Message Error
  • Error Line 54, Column 54: document type does not allow element "center" here
    …ode = "/";  var loadingText = "<center><img alt='loading' src='http://bomtan.o…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 59, Column 32: document type does not allow element "center" here
    			//var loadingText = "<center><img src='http://bomtan.org/images/loading.gif'…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 98, Column 166: character "'" is not allowed in the value of attribute "id"
    …tion(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style="width:72…

    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 98, Column 167: value of attribute "id" must be a single token
    …ion(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style="width:728…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 98, Column 168: character "+" is not allowed in the value of attribute "id"
    …on(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style="width:728p…

    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 98, Column 186: character "+" is not allowed in the value of attribute "id"
    …pan id="kauli_yad_' + kauli_yad_count + '" style="width:728px; height:90px; di…

    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 98, Column 188: character "'" is not allowed in the value of attribute "id"
    …n id="kauli_yad_' + kauli_yad_count + '" style="width:728px; height:90px; disp…

    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 98, Column 245: document type does not allow element "span" here
    …px; height:90px; display:inline-block"><' + '!--33264--' + '><' + '/span>'); v…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 98, Column 246: character "<" is the first character of a delimiter but occurred as data
    …x; height:90px; display:inline-block"><' + '!--33264--' + '><' + '/span>'); va…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 98, Column 268: character "<" is the first character of a delimiter but occurred as data
    …y:inline-block"><' + '!--33264--' + '><' + '/span>'); var s = d.createElement(…

    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 98, Column 488: end tag for "span" omitted, but OMITTAG NO was specified
    …ttp://js.kau.li/yad.js'; h.insertBefore(s, h.firstChild);})(document);</script>

    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 98, Column 146: start tag was here
    …_yad_count + 1;(function(d){ d.write('<span id="kauli_yad_' + kauli_yad_count …
  • Error Line 1375, Column 166: character "'" is not allowed in the value of attribute "id"
    …tion(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style="width:46…

    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 1375, Column 167: value of attribute "id" must be a single token
    …ion(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style="width:468…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 1375, Column 168: character "+" is not allowed in the value of attribute "id"
    …on(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style="width:468p…

    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 1375, Column 186: character "+" is not allowed in the value of attribute "id"
    …pan id="kauli_yad_' + kauli_yad_count + '" style="width:468px; height:60px; di…

    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 1375, Column 188: character "'" is not allowed in the value of attribute "id"
    …n id="kauli_yad_' + kauli_yad_count + '" style="width:468px; height:60px; disp…

    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 1375, Column 156: ID "kauli_yad_' + kauli_yad_count + '" already defined
    … + 1;(function(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style…

    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 98, Column 156: ID "kauli_yad_' + kauli_yad_count + '" first defined here
    … + 1;(function(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style…
  • Error Line 1375, Column 245: document type does not allow element "span" here
    …px; height:60px; display:inline-block"><' + '!--33266--' + '><' + '/span>'); v…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 1375, Column 246: character "<" is the first character of a delimiter but occurred as data
    …x; height:60px; display:inline-block"><' + '!--33266--' + '><' + '/span>'); va…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1375, Column 268: character "<" is the first character of a delimiter but occurred as data
    …y:inline-block"><' + '!--33266--' + '><' + '/span>'); var s = d.createElement(…

    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 1375, Column 488: end tag for "span" omitted, but OMITTAG NO was specified
    …ttp://js.kau.li/yad.js'; h.insertBefore(s, h.firstChild);})(document);</script>

    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 1375, Column 146: start tag was here
    …_yad_count + 1;(function(d){ d.write('<span id="kauli_yad_' + kauli_yad_count …
  • Error Line 1399, Column 38: there is no attribute "data-target"
    							<div class="tabs" data-target="#tab-dienvien .tabs-content">

    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 1400, Column 36: there is no attribute "data-name"
    								<div class="tab" data-name="dien-vien-noi-bat">Nổi bật</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 1598, Column 166: character "'" is not allowed in the value of attribute "id"
    …tion(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style="width:30…

    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 1598, Column 167: value of attribute "id" must be a single token
    …ion(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style="width:300…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 1598, Column 168: character "+" is not allowed in the value of attribute "id"
    …on(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style="width:300p…

    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 1598, Column 186: character "+" is not allowed in the value of attribute "id"
    …pan id="kauli_yad_' + kauli_yad_count + '" style="width:300px; height:250px; d…

    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 1598, Column 188: character "'" is not allowed in the value of attribute "id"
    …n id="kauli_yad_' + kauli_yad_count + '" style="width:300px; height:250px; dis…

    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 1598, Column 156: ID "kauli_yad_' + kauli_yad_count + '" already defined
    … + 1;(function(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style…

    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 98, Column 156: ID "kauli_yad_' + kauli_yad_count + '" first defined here
    … + 1;(function(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style…
  • Error Line 1598, Column 246: document type does not allow element "span" here
    …x; height:250px; display:inline-block"><' + '!--33262--' + '><' + '/span>'); v…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 1598, Column 247: character "<" is the first character of a delimiter but occurred as data
    …; height:250px; display:inline-block"><' + '!--33262--' + '><' + '/span>'); va…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1598, Column 269: character "<" is the first character of a delimiter but occurred as data
    …y:inline-block"><' + '!--33262--' + '><' + '/span>'); var s = d.createElement(…

    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 1598, Column 489: end tag for "span" omitted, but OMITTAG NO was specified
    …ttp://js.kau.li/yad.js'; h.insertBefore(s, h.firstChild);})(document);</script>

    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 1598, Column 146: start tag was here
    …_yad_count + 1;(function(d){ d.write('<span id="kauli_yad_' + kauli_yad_count …
  • Warning Line 1609, Column 165: cannot generate system identifier for general entity "zs"
    …ite.com/mb/text_group.php?sid=2247637&zs=3330305f323530&ifr='+AdBrite_Iframe+'…

    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 1609, Column 165: general entity "zs" not defined and no default entity
    …ite.com/mb/text_group.php?sid=2247637&zs=3330305f323530&ifr='+AdBrite_Iframe+'…

    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 1609, Column 167: reference not terminated by REFC delimiter
    …e.com/mb/text_group.php?sid=2247637&zs=3330305f323530&ifr='+AdBrite_Iframe+'&r…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 1609, Column 167: reference to entity "zs" for which no system identifier could be generated
    …e.com/mb/text_group.php?sid=2247637&zs=3330305f323530&ifr='+AdBrite_Iframe+'&r…

    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 1609, Column 164: entity was defined here
    …rite.com/mb/text_group.php?sid=2247637&zs=3330305f323530&ifr='+AdBrite_Iframe+…
  • Warning Line 1609, Column 183: cannot generate system identifier for general entity "ifr"
    …oup.php?sid=2247637&zs=3330305f323530&ifr='+AdBrite_Iframe+'&ref='+AdBrite_Ref…

    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 1609, Column 183: general entity "ifr" not defined and no default entity
    …oup.php?sid=2247637&zs=3330305f323530&ifr='+AdBrite_Iframe+'&ref='+AdBrite_Ref…

    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 1609, Column 186: reference not terminated by REFC delimiter
    ….php?sid=2247637&zs=3330305f323530&ifr='+AdBrite_Iframe+'&ref='+AdBrite_Referr…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 1609, Column 186: reference to entity "ifr" for which no system identifier could be generated
    ….php?sid=2247637&zs=3330305f323530&ifr='+AdBrite_Iframe+'&ref='+AdBrite_Referr…

    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 1609, Column 182: entity was defined here
    …roup.php?sid=2247637&zs=3330305f323530&ifr='+AdBrite_Iframe+'&ref='+AdBrite_Re…
  • Warning Line 1609, Column 206: cannot generate system identifier for general entity "ref"
    …3330305f323530&ifr='+AdBrite_Iframe+'&ref='+AdBrite_Referrer+'&purl='+encodeUR…

    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 1609, Column 206: general entity "ref" not defined and no default entity
    …3330305f323530&ifr='+AdBrite_Iframe+'&ref='+AdBrite_Referrer+'&purl='+encodeUR…

    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 1609, Column 209: reference not terminated by REFC delimiter
    …0305f323530&ifr='+AdBrite_Iframe+'&ref='+AdBrite_Referrer+'&purl='+encodeURICo…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 1609, Column 209: reference to entity "ref" for which no system identifier could be generated
    …0305f323530&ifr='+AdBrite_Iframe+'&ref='+AdBrite_Referrer+'&purl='+encodeURICo…

    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 1609, Column 205: entity was defined here
    …=3330305f323530&ifr='+AdBrite_Iframe+'&ref='+AdBrite_Referrer+'&purl='+encodeU…
  • Warning Line 1609, Column 231: cannot generate system identifier for general entity "purl"
    …ite_Iframe+'&ref='+AdBrite_Referrer+'&purl='+encodeURIComponent(AdBrite_Page_U…

    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 1609, Column 231: general entity "purl" not defined and no default entity
    …ite_Iframe+'&ref='+AdBrite_Referrer+'&purl='+encodeURIComponent(AdBrite_Page_U…

    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 1609, Column 235: reference not terminated by REFC delimiter
    …Iframe+'&ref='+AdBrite_Referrer+'&purl='+encodeURIComponent(AdBrite_Page_Url)+…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 1609, Column 235: reference to entity "purl" for which no system identifier could be generated
    …Iframe+'&ref='+AdBrite_Referrer+'&purl='+encodeURIComponent(AdBrite_Page_Url)+…

    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 1609, Column 230: entity was defined here
    …rite_Iframe+'&ref='+AdBrite_Referrer+'&purl='+encodeURIComponent(AdBrite_Page_…
  • Warning Line 1610, Column 95: cannot generate system identifier for general entity "afsid"
    …mmerce/purchase_form.php?opid=2247637&afsid=1" style="font-weight:bold;font-fa…

    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 1610, Column 95: general entity "afsid" not defined and no default entity
    …mmerce/purchase_form.php?opid=2247637&afsid=1" style="font-weight:bold;font-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.

  • Warning Line 1610, Column 100: reference not terminated by REFC delimiter
    …e/purchase_form.php?opid=2247637&afsid=1" style="font-weight:bold;font-family:…

    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 1610, Column 100: reference to external entity in attribute value
    …e/purchase_form.php?opid=2247637&afsid=1" style="font-weight:bold;font-family:…

    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 1610, Column 100: reference to entity "afsid" for which no system identifier could be generated
    …e/purchase_form.php?opid=2247637&afsid=1" style="font-weight:bold;font-family:…

    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 1610, Column 94: entity was defined here
    …ommerce/purchase_form.php?opid=2247637&afsid=1" style="font-weight:bold;font-f…
  • Error Line 2106, Column 13: 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 2113, Column 41: there is no attribute "data-href"
    …			<div class="fb-like-box" data-href="https://www.facebook.com/BomTanOrg" 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 2113, Column 89: there is no attribute "data-width"
    …ww.facebook.com/BomTanOrg" data-width="300" data-height="300" data-show-faces=…

    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 2113, Column 107: there is no attribute "data-height"
    …mTanOrg" data-width="300" data-height="300" data-show-faces="true" data-border…

    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 2113, Column 129: there is no attribute "data-show-faces"
    …00" data-height="300" data-show-faces="true" data-border-color="#111111" data-…

    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 2113, Column 154: there is no attribute "data-border-color"
    …a-show-faces="true" data-border-color="#111111" data-stream="false" data-heade…

    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 2113, Column 176: there is no attribute "data-stream"
    …true" data-border-color="#111111" 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 2113, Column 196: there is no attribute "data-header"
    …true" data-border-color="#111111" 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 2134, Column 23: required attribute "type" not specified
    		<script id="_wau27u">var _wau = _wau || []; _wau.push(["classic", "8a98wtrb5c…

    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 2170, Column 37: there is no attribute "typeof"
    		<div style="display:none;" typeof="v:Review-aggregate" xmlns:v="http://rdf.da…

    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 2171, Column 19: there is no attribute "property"
    			<span property="v:itemreviewed">BomTan.Org trang phim trực tuyến tốc độ cao<…

    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 2172, Column 14: there is no attribute "rel"
    			<span rel="v:rating"> 

    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 2173, Column 18: there is no attribute "typeof"
    				<span typeof="v:Rating"> 

    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 2207, Column 166: character "'" is not allowed in the value of attribute "id"
    …tion(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style="width:16…

    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 2207, Column 167: value of attribute "id" must be a single token
    …ion(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style="width:160…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 2207, Column 168: character "+" is not allowed in the value of attribute "id"
    …on(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style="width:160p…

    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 2207, Column 186: character "+" is not allowed in the value of attribute "id"
    …pan id="kauli_yad_' + kauli_yad_count + '" style="width:160px; height:600px; d…

    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 2207, Column 188: character "'" is not allowed in the value of attribute "id"
    …n id="kauli_yad_' + kauli_yad_count + '" style="width:160px; height:600px; dis…

    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 2207, Column 156: ID "kauli_yad_' + kauli_yad_count + '" already defined
    … + 1;(function(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style…

    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 98, Column 156: ID "kauli_yad_' + kauli_yad_count + '" first defined here
    … + 1;(function(d){ d.write('<span id="kauli_yad_' + kauli_yad_count + '" style…
  • Error Line 2207, Column 246: document type does not allow element "span" here
    …x; height:600px; display:inline-block"><' + '!--33261--' + '><' + '/span>'); v…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 2207, Column 247: character "<" is the first character of a delimiter but occurred as data
    …; height:600px; display:inline-block"><' + '!--33261--' + '><' + '/span>'); va…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 2207, Column 269: character "<" is the first character of a delimiter but occurred as data
    …y:inline-block"><' + '!--33261--' + '><' + '/span>'); var s = d.createElement(…

    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 2207, Column 489: end tag for "span" omitted, but OMITTAG NO was specified
    …ttp://js.kau.li/yad.js'; h.insertBefore(s, h.firstChild);})(document);</script>

    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 2207, Column 146: start tag was here
    …_yad_count + 1;(function(d){ d.write('<span id="kauli_yad_' + kauli_yad_count …
  • Error Line 2231, Column 194: required attribute "alt" not specified
    …ery.adnetwork.vn/247/noscript/zid_1351657424/wid_1344302689/" /></a></noscript>

    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 2245, Column 97: end tag for "ol" which is not finished
    …c| 2100.242 kb | Query: 0 | IP: 128.30.52.70 | Location: US<br/><ol></ol></div>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

Visitor Analysis

Daily Visitor
  • 1.750 visits
Daily Visitor