NaaiBuddies:: South Africa's No.1 fun dating site! Our members just want to meet and have fun. Meet girls looking for NaaiBuddies in your area today. Find NaaiBuddies. ...

naaibuddies.com
  • Domain Name
    naaibuddies.com
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #28505
  • Page Size
    15.5 KB
  • Ip Address
    77.92.78.246
  • Heading
    H1: 1, H2: 3, H3: 2, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 9 JPG, 1 PNG

Website Meta Analysis

  • Title
    Naaibuddies
  • Meta Keyword
    dating, naaibuddies, meet girls, meet women, south africa, south african girls, buddy, choty goty, cape, Find NaaiBuddies
  • Meta Description
    NaaiBuddies:: South Africa's No.1 fun dating site! Our members just want to meet and have fun. Meet girls looking for NaaiBuddies in your area today. Find NaaiBuddies.

Technical Analysis

  • Webserver
    Apache/2.2.24 (Unix) mod_ssl/2.2.24 OpenSSL/1.0.0-fips mod_bwlimited/1.4
  • Ip Address
    77.92.78.246
  • Domain Age
    1 Years, 3 Months, 27 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache/2.2.24 (Unix) mod_ssl/2.2.24 OpenSSL/1.0.0-fips mod_bwlimited/1.4
  • x-powered-by: PHP/5.3.26
  • cache-control: max-age=60, private, proxy-revalidate
  • content-type: text/html
  • content-encoding: gzip
  • content-length: 4504
  • accept-ranges: bytes
  • date: Wed, 24 Sep 2014 12:56:46 GMT
  • x-varnish: 463674215 463673634
  • age: 29
  • via: 1.1 varnish
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
******************************************************************
Registrar: 123Reg/Webfusion
Url: http://www.123-reg.co.uk/domain-names/

This domain is provided by 123-reg. We're the UK's largest
registrar with over 3 million domains sold. We also provide
cheap, easy website creation.
******************************************************************

Domain Name: NAAIBUDDIES.COM
Created Date: 12-Nov-2011
Expiry Date: 12-Nov-2013
Nameserver: ns.123-reg.co.uk
Nameserver: ns2.123-reg.co.uk
Registrant Name: Identity Protection Service
Registrant Company: Identity Protect Limited
Registrant Address: PO Box 795
Registrant Address:
Registrant Address:
Registrant Address: Godalming
Registrant Address: Surrey
Registrant Address: GU7 9GA
Registrant Address: United Kingdom
Technical Name: Identity Protection Service
Technical Company: Identity Protect Limited
Technical Address: PO Box 795
Technical Address:
Technical Address:
Technical Address: Godalming
Technical Address: Surrey
Technical Address: GU7 9GA
Technical Address: United Kingdom
Technical Email: email
Technical Tel: +44.1483307527
Technical Fax: +44.1483304031
Administrative Name: Identity Protection Service
Administrative Company: Identity Protect Limited
Administrative Address: PO Box 795
Administrative Address:
Administrative Address:
Administrative Address: Godalming
Administrative Address: Surrey
Administrative Address: GU7 9GA
Administrative Address: United Kingdom
Administrative Email: email
Administrative Tel: +44.1483307527
Administrative Fax: +44.1483304031

The Data in this WHOIS database is provided
for information purposes only, and is designed to assist persons in
obtaining information related to domain name registration records.
It's accuracy is not guarenteed. By submitting a
WHOIS query, you agree that you will use this Data only for lawful
purposes and that, under no circumstances will you use this Data to:
(1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail(spam);
or (2) enable high volume, automated, electronic processes that
apply to this WHOIS or any of its related systems. The provider of
this WHOIS reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by this policy.

LACK OF A DOMAIN RECORD IN THE WHOIS DATABASE DOES
NOT INDICATE DOMAIN AVAILABILITY.

DNS Analysis


DNS servers
ns2.123-reg.co.uk [92.51.159.40]
ns.123-reg.co.uk [212.67.202.2]


DNS Records

Answer records
naaibuddies.com SOA
server: ns.123-reg.co.uk
email: hostmaster@naaibuddies.com
serial: 2011112101
refresh: 86400
retry: 7200
expire: 604800
minimum ttl: 86400
10800s
naaibuddies.com NS  ns2.123-reg.co.uk 86400s
naaibuddies.com NS  ns.123-reg.co.uk 86400s
naaibuddies.com A 83.170.89.42 86400s

Authority records

Additional records
ns.123-reg.co.uk A 212.67.202.2 300s
ns2.123-reg.co.uk A 92.51.159.40 300s

IP 77.92.78.246 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 2 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.6137796268280383
Message Error
  • Warning Line 7, Column 132: cannot generate system identifier for general entity "keyword"
    …p://www.naaibuddies.com/m/aindex.php?&keyword=Meet+Local+Women+Desperate+For+A…

    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 "&" (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 æ 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 7, Column 132: general entity "keyword" not defined and no default entity
    …p://www.naaibuddies.com/m/aindex.php?&keyword=Meet+Local+Women+Desperate+For+A…

    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 7, Column 139: reference not terminated by REFC delimiter
    ….naaibuddies.com/m/aindex.php?&keyword=Meet+Local+Women+Desperate+For+Adult+Fu…

    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 7, Column 139: reference to external entity in attribute value
    ….naaibuddies.com/m/aindex.php?&keyword=Meet+Local+Women+Desperate+For+Adult+Fu…

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

  • Error Line 7, Column 139: reference to entity "keyword" for which no system identifier could be generated
    ….naaibuddies.com/m/aindex.php?&keyword=Meet+Local+Women+Desperate+For+Adult+Fu…

    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 7, Column 131: entity was defined here
    …tp://www.naaibuddies.com/m/aindex.php?&keyword=Meet+Local+Women+Desperate+For+…
  • Warning Line 7, Column 182: cannot generate system identifier for general entity "utm_source"
    …yword=Meet+Local+Women+Desperate+For+Adult+Fun.&utm_source=redirein2"></script>

    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 7, Column 182: general entity "utm_source" not defined and no default entity
    …yword=Meet+Local+Women+Desperate+For+Adult+Fun.&utm_source=redirein2"></script>

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

  • Warning Line 7, Column 192: reference not terminated by REFC delimiter
    …yword=Meet+Local+Women+Desperate+For+Adult+Fun.&utm_source=redirein2"></script>

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

  • Warning Line 7, Column 192: reference to external entity in attribute value
    …yword=Meet+Local+Women+Desperate+For+Adult+Fun.&utm_source=redirein2"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 7, Column 192: reference to entity "utm_source" for which no system identifier could be generated
    …yword=Meet+Local+Women+Desperate+For+Adult+Fun.&utm_source=redirein2"></script>

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

  • Info Line 7, Column 181: entity was defined here
    …yword=Meet+Local+Women+Desperate+For+Adult+Fun.&utm_source=redirein2"></script>
  • Error Line 7, Column 203: required attribute "type" not specified
    …yword=Meet+Local+Women+Desperate+For+Adult+Fun.&utm_source=redirein2"></script>

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

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

  • Error Line 13, Column 204: end tag for "meta" omitted, but OMITTAG NO was specified
    …fun. Meet girls looking for NaaiBuddies in your area today. Find NaaiBuddies.">

    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 13, Column 1: start tag was here
    <meta name="description" content="NaaiBuddies:: South Africa's No.1 fun dating …
  • Error Line 15, Column 155: end tag for "meta" omitted, but OMITTAG NO was specified
    … south africa, south african girls, buddy, choty goty, cape, Find NaaiBuddies">

    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 15, Column 1: start tag was here
    <meta name="keywords" content="dating, naaibuddies, meet girls, meet women, sou…
  • Error Line 46, Column 30: required attribute "type" not specified
    <script language="javascript">

    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 86, Column 63: NET-enabling start-tag not immediately followed by null end-tag
    …g"><img src="images/naaibuddies.gif" /trampstamp-logo.jpg" alt="Naai Buddies" …

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 86, Column 63: required attribute "alt" not specified
    …g"><img src="images/naaibuddies.gif" /trampstamp-logo.jpg" alt="Naai Buddies" …

    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 86, Column 63: end tag for "img" omitted, but OMITTAG NO was specified
    …g"><img src="images/naaibuddies.gif" /trampstamp-logo.jpg" alt="Naai Buddies" …

    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 86, Column 28: start tag was here
        <div class="headerimg"><img src="images/naaibuddies.gif" /trampstamp-logo.j…
  • Error Line 86, Column 202: required attribute "alt" not specified
    …img src="images/south_africa.gif" style="position:relative; top:-10px;"/></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 104, Column 84: there is no attribute "onFocus"
    …lue="Email address/Member ID" onFocus='if(this.value=="Email address/Member ID…

    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 108, Column 99: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"
    …loginbutton" style="width:45px;" align="absmiddle" src="images/loginbtn.jpg" />

    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 148, Column 95: syntax of attribute value does not conform to declared value
    …"reg" method="post" action="http://local.naaibuddies.com/signup.cfm" target="">

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 179, Column 29: document type does not allow element "div" here; missing one of "th", "td" start-tag
    				<div style="width:305px">

    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 180, Column 26: document type does not allow element "td" here
    		        <td width="30%"><label>I&#39;m a:</label></td>

    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 181, Column 39: value of attribute "align" cannot be "RIGHT"; must be one of "left", "center", "right", "justify", "char"
    		        <td width="70%" align="RIGHT"><select name="gender" style="width:222p…

    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 181, Column 40: document type does not allow element "td" here
    …	        <td width="70%" align="RIGHT"><select name="gender" style="width:222p…

    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 183, Column 39: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    		          <option value="1" selected>man looking for a woman</option>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 189, Column 14: end tag for "tr" which is not finished
    	        </tr>

    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.

  • Error Line 195, Column 27: value of attribute "align" cannot be "RIGHT"; must be one of "left", "center", "right", "justify", "char"
    		        <td align="RIGHT"><input name="firstname" type="text" size="29" /></t…

    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 484, Column 33: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    	        	<div id="continue-btn">

    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 485, Column 42: there is no attribute "SRC"
    …      	  <div align="center"><img SRC="images/continuebt.gif" BORDER="0" ALT="…

    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 485, Column 73: there is no attribute "BORDER"
    …lign="center"><img SRC="images/continuebt.gif" BORDER="0" ALT="Continue"></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 485, Column 81: there is no attribute "ALT"
    …lign="center"><img SRC="images/continuebt.gif" BORDER="0" ALT="Continue"></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 485, Column 91: required attribute "src" not specified
    …lign="center"><img SRC="images/continuebt.gif" BORDER="0" ALT="Continue"></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 485, Column 91: required attribute "alt" not specified
    …lign="center"><img SRC="images/continuebt.gif" BORDER="0" ALT="Continue"></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 485, Column 97: end tag for "img" omitted, but OMITTAG NO was specified
    …lign="center"><img SRC="images/continuebt.gif" BORDER="0" ALT="Continue"></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 485, Column 33: start tag was here
    	        	  <div align="center"><img SRC="images/continuebt.gif" BORDER="0" ALT…
  • Error Line 496, Column 32: document type does not allow element "div" here; missing one of "th", "td" start-tag
    							<div style="width:305px">

    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 497, Column 14: document type does not allow element "td" here
    		        <td><label>Email:</label></td>

    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 499, Column 27: value of attribute "align" cannot be "RIGHT"; must be one of "left", "center", "right", "justify", "char"
    		        <td align="RIGHT"><input name="email" type="text" size="29" /></td>

    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 499, Column 28: document type does not allow element "td" here
    		        <td align="RIGHT"><input name="email" type="text" size="29" /></td>

    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 502, Column 14: end tag for "tr" which is not finished
    	        </tr>

    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.

  • Error Line 506, Column 27: value of attribute "align" cannot be "RIGHT"; must be one of "left", "center", "right", "justify", "char"
    		        <td align="RIGHT"><label>Password:</label></td>

    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 527, Column 45: there is no attribute "TYPE"
    …      <div align="center"><INPUT TYPE="image" SRC="images/signup_free_dating.g…

    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 527, Column 57: there is no attribute "SRC"
    …lign="center"><INPUT TYPE="image" SRC="images/signup_free_dating.gif" 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 527, Column 96: there is no attribute "BORDER"
    … TYPE="image" SRC="images/signup_free_dating.gif" BORDER="0" ALT="Submit Form">

    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 527, Column 104: there is no attribute "ALT"
    … TYPE="image" SRC="images/signup_free_dating.gif" BORDER="0" ALT="Submit Form">

    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 527, Column 117: element "INPUT" undefined
    … TYPE="image" SRC="images/signup_free_dating.gif" BORDER="0" ALT="Submit Form">

    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 529, Column 8: end tag for "INPUT" omitted, but OMITTAG NO was specified
    		</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 527, Column 33: start tag was here
                <div align="center"><INPUT TYPE="image" SRC="images/signup_free_dat…
  • Error Line 533, Column 12: end tag for "div" omitted, but OMITTAG NO was specified
    	</fieldset> 

    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 493, Column 2: start tag was here
    	<div id="example" class="more">
  • Error Line 533, Column 12: end tag for "div" omitted, but OMITTAG NO was specified
    	</fieldset> 

    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 3: start tag was here
    		<div> 
  • Error Line 747, Column 16: end tag for "td" omitted, but OMITTAG NO was specified
              </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 743, Column 11: start tag was here
              <td width="50%" align="justify" valign="top" style="padding-left:10px…
  • Error Line 747, Column 16: end tag for "tr" omitted, but OMITTAG NO was specified
              </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 713, Column 9: start tag was here
            <tr>
  • Error Line 747, Column 16: end tag for "table" omitted, but OMITTAG NO was specified
              </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 711, Column 11: start tag was here
          <td><table width="100%" border="0">
  • Error Line 747, Column 16: end tag for "td" omitted, but OMITTAG NO was specified
              </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 711, Column 7: start tag was here
          <td><table width="100%" border="0">
  • Error Line 747, Column 16: end tag for "tr" omitted, but OMITTAG NO was specified
              </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 709, Column 5: start tag was here
        <tr>
  • Error Line 747, Column 16: end tag for "table" omitted, but OMITTAG NO was specified
              </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 701, Column 3: start tag was here
      <table width="100%" border="0">
  • Error Line 765, Column 5: end tag for element "td" which is not open
    </td>

    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 767, Column 13: end tag for element "tr" which is not open
            </tr>

    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 769, Column 14: end tag for element "table" which is not open
          </table></td>

    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 769, Column 19: end tag for element "td" which is not open
          </table></td>

    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 771, Column 9: end tag for element "tr" which is not open
        </tr>

    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 773, Column 8: document type does not allow element "tr" here; assuming missing "table" start-tag
        <tr>
  • Error Line 802, Column 11: end tag for "p" omitted, but OMITTAG NO was specified
          </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 799, Column 7: start tag was here
          <p>
  • Error Line 808, Column 6: end tag for element "div" which is not open
    </div>

    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.

  • Warning Line 838, Column 121: character "&" is the first character of a delimiter but occurred as data
    …st+"/api/tracking/?site="+wld_siteId+"&"+wld_trackingVars+"' type='text/javasc…

    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 842, Column 9: end tag for "div" omitted, but OMITTAG NO was specified
      </body>

    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 810, Column 1: start tag was here
    <div class="footerwrap">

Visitor Analysis

Daily Visitor
  • 5.250 visits