giaitrichat.com

GiaiTri.com ,  BaoNail.com ,  RenewBang.com ,  VinaMax.com      Đăng kí gia nhập thành viên ,  Danh sách thành viên ,  Quên mật mã tài khoản ,  Nội quy dành cho Admin, Mod Khóa: Nick: Mật mã: Chat 1   Chat ...

Display Widget for this domain on your website. Click Here
This data was last updated from 17-09-2013 11:00:59  (update).

Overview Info

  • Domain Name
    giaitrichat.com
  • Favicon
  • Alexa Rank
    #3267188
  • Google Page Rank
    PR 1
  • Ip Address
    65.99.204.111
  • Page Size
    8.4 KB
  • Images
    3 GIF, 0 JPG, 3 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    Đăng nhập GiaiTriCHAT
  • Meta Keyword
  • Meta Description
    GiaiTri.com ,  BaoNail.com ,  RenewBang.com ,  VinaMax.com      Đăng kí gia nhập thành viên ,  Danh sách thành viên ,  Quên mật mã tài khoản ,  Nội quy dành cho Admin, Mod Khóa: Nick: Mật mã: Chat 1   Chat 2 Xin hãy điền Nick chat vào ô trống, ...

Technical Analysis



  • Webserver
    Apache/2.2.3 (Red Hat)
  • Ip Address
    65.99.204.111
  • Domain Age
    5 Years, 11 Months, 21 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Tue, 17 Sep 2013 23:00:55 GMT
  • server: Apache/2.2.3 (Red Hat)
  • x-powered-by: PHP/5.1.6
  • 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
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for giaitrichat.com

DNS Analysis


DNS servers
ns23.domaincontrol.com [216.69.185.12]
ns24.domaincontrol.com [208.109.255.12]


DNS Records

Answer records
giaitrichat.com A 65.99.204.111 3600s
giaitrichat.com MX
preference: 0
exchange: smtp.secureserver.net
3600s
giaitrichat.com MX
preference: 10
exchange: mailstore1.secureserver.net
3600s
giaitrichat.com NS  NS23.DOMAINCONTROL.com 3600s
giaitrichat.com NS  ns24.domaincontrol.com 3600s
giaitrichat.com SOA
server: ns23.domaincontrol.com
email: dns@jomax.net
serial: 2009051900
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records

IP 65.99.204.111 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 72 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.5528644620400559
Message Error
  • Error Line 13, Column 22: there is no attribute "LANGUAGE"
        <SCRIPT LANGUAGE="JavaScript">

    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 13, Column 34: element "SCRIPT" undefined
        <SCRIPT LANGUAGE="JavaScript">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 41, Column 49: cannot generate system identifier for general entity "login"
    …      var dataString = 'func=login_in&login='+ login + '&password=' + password…

    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 41, Column 49: general entity "login" not defined and no default entity
    …      var dataString = 'func=login_in&login='+ login + '&password=' + password…

    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 41, Column 54: reference not terminated by REFC delimiter
    … var dataString = 'func=login_in&login='+ login + '&password=' + password + '&…

    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 41, Column 54: reference to entity "login" for which no system identifier could be generated
    … var dataString = 'func=login_in&login='+ login + '&password=' + password + '&…

    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 41, Column 48: entity was defined here
    …       var dataString = 'func=login_in&login='+ login + '&password=' + passwor…
  • Warning Line 41, Column 68: cannot generate system identifier for general entity "password"
    …g = 'func=login_in&login='+ login + '&password=' + password + '&enter=' + ente…

    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 41, Column 68: general entity "password" not defined and no default entity
    …g = 'func=login_in&login='+ login + '&password=' + password + '&enter=' + ente…

    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 41, Column 76: reference not terminated by REFC delimiter
    …c=login_in&login='+ login + '&password=' + password + '&enter=' + enter + '&ms…

    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 41, Column 76: reference to entity "password" for which no system identifier could be generated
    …c=login_in&login='+ login + '&password=' + password + '&enter=' + enter + '&ms…

    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 41, Column 67: entity was defined here
    …ng = 'func=login_in&login='+ login + '&password=' + password + '&enter=' + ent…
  • Warning Line 41, Column 94: cannot generate system identifier for general entity "enter"
    …+ login + '&password=' + password + '&enter=' + enter + '&mstring='+mstring+ '…

    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 41, Column 94: general entity "enter" not defined and no default entity
    …+ login + '&password=' + password + '&enter=' + enter + '&mstring='+mstring+ '…

    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 41, Column 99: reference not terminated by REFC delimiter
    …in + '&password=' + password + '&enter=' + enter + '&mstring='+mstring+ '&ccod…

    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 41, Column 99: reference to entity "enter" for which no system identifier could be generated
    …in + '&password=' + password + '&enter=' + enter + '&mstring='+mstring+ '&ccod…

    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 41, Column 93: entity was defined here
    …'+ login + '&password=' + password + '&enter=' + enter + '&mstring='+mstring+ …
  • Warning Line 41, Column 114: cannot generate system identifier for general entity "mstring"
    …=' + password + '&enter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + '…

    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 41, Column 114: general entity "mstring" not defined and no default entity
    …=' + password + '&enter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + '…

    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 41, Column 121: reference not terminated by REFC delimiter
    …ssword + '&enter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + '&cserve…

    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 41, Column 121: reference to entity "mstring" for which no system identifier could be generated
    …ssword + '&enter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + '&cserve…

    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 41, Column 113: entity was defined here
    …d=' + password + '&enter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + …
  • Warning Line 41, Column 135: cannot generate system identifier for general entity "ccode"
    …ter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + '&cserver=' + cserver;

    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 41, Column 135: general entity "ccode" not defined and no default entity
    …ter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + '&cserver=' + cserver;

    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 41, Column 140: reference not terminated by REFC delimiter
    …ter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + '&cserver=' + cserver;

    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 41, Column 140: reference to entity "ccode" for which no system identifier could be generated
    …ter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + '&cserver=' + cserver;

    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 41, Column 134: entity was defined here
    …ter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + '&cserver=' + cserver…
  • Warning Line 41, Column 155: cannot generate system identifier for general entity "cserver"
    …ter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + '&cserver=' + cserver;

    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 41, Column 155: general entity "cserver" not defined and no default entity
    …ter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + '&cserver=' + cserver;

    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 41, Column 162: reference not terminated by REFC delimiter
    …ter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + '&cserver=' + cserver;

    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 41, Column 162: reference to entity "cserver" for which no system identifier could be generated
    …ter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + '&cserver=' + cserver;

    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 41, Column 154: entity was defined here
    …ter=' + enter + '&mstring='+mstring+ '&ccode=' + ccode + '&cserver=' + cserver;
  • Warning Line 52, Column 39: character "&" is the first character of a delimiter but occurred as data
                                if(!ccode && data!='error14')

    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 52, Column 40: character "&" is the first character of a delimiter but occurred as data
                                if(!ccode && data!='error14')

    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 103, Column 44: end tag for "br" omitted, but OMITTAG NO was specified
    		Error['error1'] = 'Mật mã không đúng,<br>xin kiểm tra lại mật mã.';

    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 103, Column 40: start tag was here
    		Error['error1'] = 'Mật mã không đúng,<br>xin kiểm tra lại mật mã.';
  • Error Line 104, Column 51: end tag for "br" omitted, but OMITTAG NO was specified
    …or2'] = "Tài khoản này đã bị khóa.<br>Khóa bỡi: <b></b>, ngày: <b></b><br><i><…

    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 104, Column 47: start tag was here
    …'error2'] = "Tài khoản này đã bị khóa.<br>Khóa bỡi: <b></b>, ngày: <b></b><br>…
  • Error Line 104, Column 87: end tag for "br" omitted, but OMITTAG NO was specified
    …] = "Tài khoản này đã bị khóa.<br>Khóa bỡi: <b></b>, ngày: <b></b><br><i></i>";

    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 104, Column 83: start tag was here
    …] = "Tài khoản này đã bị khóa.<br>Khóa bỡi: <b></b>, ngày: <b></b><br><i></i>";
  • Error Line 105, Column 49: end tag for "br" omitted, but OMITTAG NO was specified
    …r['error3'] = 'Nick này đã đăng kí,<br>xin chọn Nick khác hoặc đăng nhập lại.';

    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 105, Column 45: start tag was here
    …rror['error3'] = 'Nick này đã đăng kí,<br>xin chọn Nick khác hoặc đăng nhập lạ…
  • Error Line 106, Column 69: end tag for "br" omitted, but OMITTAG NO was specified
    …>"@"</b> chỉ dành cho Mod và Admin.<br>Xin hãy đăng nhập hoặc chọn nick khác.';

    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 106, Column 65: start tag was here
    … <b>"@"</b> chỉ dành cho Mod và Admin.<br>Xin hãy đăng nhập hoặc chọn nick khá…
  • Error Line 107, Column 68: end tag for "br" omitted, but OMITTAG NO was specified
    …y đã có TViên khác sử đang sử dụng.<br>Xin hãy đăng nhập hoặc chọn nick khác.';

    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 107, Column 64: start tag was here
    … này đã có TViên khác sử đang sử dụng.<br>Xin hãy đăng nhập hoặc chọn nick khá…
  • Error Line 112, Column 81: end tag for element "br" which is not open
    …n bạn vui lòng chọn Nick ngắn hơn. </br>  Nick được giới hạn đến 25 ký tự .  ";

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 119, Column 60: end tag for "link" omitted, but OMITTAG NO was specified
        <link rel='stylesheet' type='text/css' href='main.css'>

    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 119, Column 5: start tag was here
        <link rel='stylesheet' type='text/css' href='main.css'>
  • Error Line 122, Column 7: required attribute "type" not specified
    <style>

    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 122, Column 7: document type does not allow element "style" here
    <style>

    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 143, Column 44: there is no attribute "target"
    …                       <div><a target="_top" href="http://giaitrichat.com"><im…

    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 143, Column 93: there is no attribute "border"
    …="http://giaitrichat.com"><img border="0" vspace="3" src="/gtc_logo1.png" vspa…

    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 143, Column 104: there is no attribute "vspace"
    …aitrichat.com"><img border="0" vspace="3" src="/gtc_logo1.png" vspace='15'></a…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 143, Column 136: duplicate specification of attribute "vspace"
    …hat.com"><img border="0" vspace="3" src="/gtc_logo1.png" vspace='15'></a></div>

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 143, Column 140: required attribute "alt" not specified
    …hat.com"><img border="0" vspace="3" src="/gtc_logo1.png" vspace='15'></a></div>

    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 143, Column 144: end tag for "img" omitted, but OMITTAG NO was specified
    …hat.com"><img border="0" vspace="3" src="/gtc_logo1.png" vspace='15'></a></div>

    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 143, Column 81: start tag was here
    …="_top" href="http://giaitrichat.com"><img border="0" vspace="3" src="/gtc_log…
  • Error Line 144, Column 46: there is no attribute "color"
                                <div><font color=red id='diverror'></font></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 144, Column 46: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                                <div><font color=red id='diverror'></font></div>
  • Error Line 144, Column 53: there is no attribute "id"
                                <div><font color=red id='diverror'></font></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 144, Column 63: element "font" undefined
                                <div><font color=red id='diverror'></font></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 145, Column 46: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                                <div><font color=red></font></div>
  • Error Line 145, Column 49: element "font" undefined
                                <div><font color=red></font></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 146, Column 106: there is no attribute "hspace"
    …mg src='images/loading-page.gif' id="loadingc" style='display:none' hspace='1'>

    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 146, Column 109: required attribute "alt" not specified
    …mg src='images/loading-page.gif' id="loadingc" style='display:none' hspace='1'>

    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 146, Column 110: end tag for "img" omitted, but OMITTAG NO was specified
    …mg src='images/loading-page.gif' id="loadingc" style='display:none' hspace='1'>

    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 146, Column 29: start tag was here
                                <img src='images/loading-page.gif' id="loadingc" st…
  • Error Line 151, Column 64: there is no attribute "name"
    …           <form id="loginForm1" name="loginForm1" method="post" action="http:…

    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 151, Column 145: there is no attribute "target"
    …m1" method="post" action="http://chat.lmvn.com/member/index.php" target="_top">

    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 152, Column 86: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …                             <input type='hidden' name='func' value='login_in'>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 152, Column 87: end tag for "input" omitted, but OMITTAG NO was specified
    …                             <input type='hidden' name='func' value='login_in'>

    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 152, Column 37: start tag was here
                                        <input type='hidden' name='func' value='log…
  • Error Line 153, Column 83: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …                                <input type='hidden' name='cookieUID' value=''>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 153, Column 84: end tag for "input" omitted, but OMITTAG NO was specified
    …                                <input type='hidden' name='cookieUID' value=''>

    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 153, Column 37: start tag was here
                                        <input type='hidden' name='cookieUID' value…
  • Error Line 154, Column 82: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …                                 <input type="hidden" value="1" name="cserver">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 154, Column 83: end tag for "input" omitted, but OMITTAG NO was specified
    …                                 <input type="hidden" value="1" name="cserver">

    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 154, Column 37: start tag was here
                                        <input type="hidden" value="1" name="cserve…
  • Error Line 155, Column 80: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                                        <input type="hidden" value="1" name="enter">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 155, Column 81: end tag for "input" omitted, but OMITTAG NO was specified
                                        <input type="hidden" value="1" name="enter">

    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 155, Column 37: start tag was here
                                        <input type="hidden" value="1" name="enter">
  • Error Line 164, Column 73: end tag for "input" omitted, but OMITTAG NO was specified
                <td><input name='ccode' type='text' id='ccode' size='3'></td>

    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 164, Column 17: start tag was here
                <td><input name='ccode' type='text' id='ccode' size='3'></td>
  • Error Line 172, Column 105: end tag for "input" omitted, but OMITTAG NO was specified
    …           		<td><input type='text' name='login' id='login' size='15' value=''>

    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 172, Column 43: start tag was here
    …                                		<td><input type='text' name='login' id='logi…
  • Error Line 174, Column 187: required attribute "alt" not specified
    …e='Thành viên đăng nhập'><img src='login.png' border='0' hspace='3'></a></span>

    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 174, Column 191: end tag for "img" omitted, but OMITTAG NO was specified
    …e='Thành viên đăng nhập'><img src='login.png' border='0' hspace='3'></a></span>

    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 174, Column 145: start tag was here
    … false;' title='Thành viên đăng nhập'><img src='login.png' border='0' hspace='…
  • Error Line 179, Column 106: end tag for "input" omitted, but OMITTAG NO was specified
    …          		<td><input type='password' name='password' id='password' size='16'>

    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 179, Column 43: start tag was here
    …                                		<td><input type='password' name='password' i…
  • Error Line 180, Column 187: required attribute "alt" not specified
    …s();return false;'><img src='pop-up-icon.gif' border='0' hspace='3'></a></span>

    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 180, Column 191: end tag for "img" omitted, but OMITTAG NO was specified
    …s();return false;'><img src='pop-up-icon.gif' border='0' hspace='3'></a></span>

    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 180, Column 139: start tag was here
    … onclick='togglepass();return false;'><img src='pop-up-icon.gif' border='0' hs…
  • Error Line 187, Column 55: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    …                    <form method='POST' action="http://chat.lmvn.com/member/in…

    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 188, Column 86: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …                             <input type='hidden' name='func' value='lostpwd1'>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 188, Column 87: end tag for "input" omitted, but OMITTAG NO was specified
    …                             <input type='hidden' name='func' value='lostpwd1'>

    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 188, Column 37: start tag was here
                                        <input type='hidden' name='func' value='los…
  • Error Line 191, Column 76: end tag for "br" omitted, but OMITTAG NO was specified
    …   <div style='padding:5px'>Nick: <br><input type='text' name='login' id='logi…

    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 191, Column 72: start tag was here
    …       <div style='padding:5px'>Nick: <br><input type='text' name='login' id='…
  • Error Line 191, Column 112: ID "login" already defined
    …x'>Nick: <br><input type='text' name='login' id='login' size='15' value=''><br>

    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 172, Column 79: ID "login" first defined here
    …           		<td><input type='text' name='login' id='login' size='15' value=''>
  • Error Line 191, Column 138: end tag for "input" omitted, but OMITTAG NO was specified
    …x'>Nick: <br><input type='text' name='login' id='login' size='15' value=''><br>

    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 191, Column 76: start tag was here
    …   <div style='padding:5px'>Nick: <br><input type='text' name='login' id='logi…
  • Error Line 191, Column 142: end tag for "br" omitted, but OMITTAG NO was specified
    …x'>Nick: <br><input type='text' name='login' id='login' size='15' value=''><br>

    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 191, Column 138: start tag was here
    …x'>Nick: <br><input type='text' name='login' id='login' size='15' value=''><br>
  • Error Line 192, Column 86: end tag for "input" omitted, but OMITTAG NO was specified
    …type='submit' value='Email' name='B1'><input type='button' value='Quay ra' nam…

    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 192, Column 41: start tag was here
    <input type='submit' value='Email' name=…
  • Error Line 192, Column 156: end tag for "input" omitted, but OMITTAG NO was specified
    …me='B1'><input type='button' value='Quay ra' name='B1' onclick='fpass()'></div>

    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 192, Column 86: start tag was here
    …type='submit' value='Email' name='B1'><input type='button' value='Quay ra' nam…
  • Error Line 199, Column 68: end tag for "br" omitted, but OMITTAG NO was specified
                                    <td colspan='2' align='center'><br>

    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 199, Column 64: start tag was here
                                    <td colspan='2' align='center'><br>
  • Error Line 200, Column 141: end tag for "br" omitted, but OMITTAG NO was specified
    …om/member/index.php?func=register'><b>Đăng kí gia nhập thành viên</b></a> ]<br>

    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 200, Column 137: start tag was here
    …om/member/index.php?func=register'><b>Đăng kí gia nhập thành viên</b></a> ]<br>
  • Error Line 201, Column 93: end tag for "br" omitted, but OMITTAG NO was specified
    …                   [ <a href='member.php'><b>Danh sách thành viên</b></a> ]<br>

    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 201, Column 89: start tag was here
    …                   [ <a href='member.php'><b>Danh sách thành viên</b></a> ]<br>
  • Error Line 202, Column 96: end tag for "br" omitted, but OMITTAG NO was specified
    …                [ <a href='javascript:fpass();'>Quên mật mã tài khoản</a> ]<br>

    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 202, Column 92: start tag was here
    …                [ <a href='javascript:fpass();'>Quên mật mã tài khoản</a> ]<br>
  • Error Line 203, Column 115: end tag for "br" omitted, but OMITTAG NO was specified
    …a href='admin_rules.htm' target='_blank'>Nội quy dành cho Admin, Mod </a> ]<br>

    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 203, Column 111: start tag was here
    …a href='admin_rules.htm' target='_blank'>Nội quy dành cho Admin, Mod </a> ]<br>
  • Error Line 209, Column 46: there is no attribute "width"
    …                 <td align='center' width='1'><img src='images/hline.png'></td>

    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 209, Column 77: required attribute "alt" not specified
    …                 <td align='center' width='1'><img src='images/hline.png'></td>

    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 209, Column 82: end tag for "img" omitted, but OMITTAG NO was specified
    …                 <td align='center' width='1'><img src='images/hline.png'></td>

    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 209, Column 50: start tag was here
    …                 <td align='center' width='1'><img src='images/hline.png'></td>
  • Error Line 212, Column 74: required attribute "alt" not specified
                            <p><img src='/gtc_ny1.png' border='0' hspace='25'></p>

    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 212, Column 78: end tag for "img" omitted, but OMITTAG NO was specified
                            <p><img src='/gtc_ny1.png' border='0' hspace='25'></p>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 212, Column 28: start tag was here
                            <p><img src='/gtc_ny1.png' border='0' hspace='25'></p>

Visitor Analysis

Daily Visitor
  • 42 visits

In Page Analysis