Submit your link on our directory for free. We are a human-edited web directory, feel free to submit multiple links. ...

addtodirectories.com
  • Domain Name
    addtodirectories.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #63667
  • Page Size
    38.4 KB
  • Ip Address
    108.175.149.11
  • Heading
    H1: 0, H2: 16, H3: 2, H4: 0, H5: 0, H6: 0
  • Images
    8 GIF, 0 JPG, 1 PNG

Website Meta Analysis

  • Title
    AddToDirectories.com - Submit your links and articles. It's free.
  • Meta Keyword
    free website links, web directory link, link directory submit, submit a url, submit to web, paid directory, paid featured listings
  • Meta Description
    Submit your link on our directory for free. We are a human-edited web directory, feel free to submit multiple links.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    108.175.149.11
  • Domain Age
    1 Years, 4 Months, 21 days.
  • Javascript Library
    jquery, prototype
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 02 Mar 2013 02:58:15 GMT
  • server: Apache
  • x-powered-by: PHP/5.2.17
  • expires: Mon, 14 Oct 2002 05:00:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • last-modified: Sat, 02 Mar 2013 02:58:16 GMT
  • content-length: 35349
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for addtodirectories.com

IP 108.175.149.11 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 108.175.149.11"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=108.175.149.11?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 108.175.144.0 - 108.175.159.255
    CIDR: 108.175.144.0/20
    OriginAS:
    NetName: ARVIXE-NETWORK-2
    NetHandle: NET-108-175-144-0-1
    Parent: NET-108-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2012-02-28
    Updated: 2012-02-28
    Ref: http://whois.arin.net/rest/net/NET-108-175-144-0-1

    OrgName: Arvixe, LLC
    OrgId: AL-102
    Address: PO Box 9202
    City: Santa Rosa
    StateProv: CA
    PostalCode: 95405
    Country: US
    RegDate: 2011-10-06
    Updated: 2011-11-18
    Ref: http://whois.arin.net/rest/org/AL-102

    OrgTechHandle: TECHN1069-ARIN
    OrgTechName: Technical Support
    OrgTechPhone: +1-707-304-5520
    OrgTechEmail:
    OrgTechRef: http://whois.arin.net/rest/poc/TECHN1069-ARIN

    OrgAbuseHandle: ABUSE3183-ARIN
    OrgAbuseName: Abuse Department
    OrgAbusePhone: +1-707-304-5520
    OrgAbuseEmail:
    OrgAbuseRef: http://whois.arin.net/rest/poc/ABUSE3183-ARIN

    OrgNOCHandle: NOC12277-ARIN
    OrgNOCName: Network Operations Center
    OrgNOCPhone: +1-707-304-5520
    OrgNOCEmail:
    OrgNOCRef: http://whois.arin.net/rest/poc/NOC12277-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 106 Errors
  • 11 Warnings
Ratio Text/Html
  • 0.5373145702093071
Message Error
  • Warning Line 28, Column 114: cannot generate system identifier for general entity "peel"
    …ipt" src="https://affiliates.arvixe.com/idevpeels.php?id=3073&peel=3"></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 28, Column 114: general entity "peel" not defined and no default entity
    …ipt" src="https://affiliates.arvixe.com/idevpeels.php?id=3073&peel=3"></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 28, Column 118: reference not terminated by REFC delimiter
    …ipt" src="https://affiliates.arvixe.com/idevpeels.php?id=3073&peel=3"></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 28, Column 118: reference to external entity in attribute value
    …ipt" src="https://affiliates.arvixe.com/idevpeels.php?id=3073&peel=3"></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 28, Column 118: reference to entity "peel" for which no system identifier could be generated
    …ipt" src="https://affiliates.arvixe.com/idevpeels.php?id=3073&peel=3"></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 28, Column 113: entity was defined here
    …ipt" src="https://affiliates.arvixe.com/idevpeels.php?id=3073&peel=3"></script>
  • Warning Line 35, Column 14: character "<" is the first character of a delimiter but occurred as data
       if (height<110) {

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

    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 266, Column 145: cannot generate system identifier for general entity "tag"
    …vL3d3dy5hZGR0b2RpcmVjdG9yaWVzLmNvbQ==&tag=1" alt="PageRank" style="border:0; p…

    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 266, Column 145: general entity "tag" not defined and no default entity
    …vL3d3dy5hZGR0b2RpcmVjdG9yaWVzLmNvbQ==&tag=1" alt="PageRank" style="border:0; p…

    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 266, Column 148: reference not terminated by REFC delimiter
    …d3dy5hZGR0b2RpcmVjdG9yaWVzLmNvbQ==&tag=1" alt="PageRank" style="border:0; padd…

    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 266, Column 148: reference to external entity in attribute value
    …d3dy5hZGR0b2RpcmVjdG9yaWVzLmNvbQ==&tag=1" alt="PageRank" style="border:0; padd…

    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 266, Column 148: reference to entity "tag" for which no system identifier could be generated
    …d3dy5hZGR0b2RpcmVjdG9yaWVzLmNvbQ==&tag=1" alt="PageRank" style="border:0; padd…

    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 266, Column 144: entity was defined here
    …ovL3d3dy5hZGR0b2RpcmVjdG9yaWVzLmNvbQ==&tag=1" alt="PageRank" style="border:0; …
  • Error Line 268, Column 9: value of attribute "id" invalid: "1" cannot start a name
    <li id="195">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 291, Column 9: value of attribute "id" invalid: "1" cannot start a name
    <li id="179">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 314, Column 9: value of attribute "id" invalid: "1" cannot start a name
    <li id="127">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 341, Column 9: value of attribute "id" invalid: "1" cannot start a name
    <li id="161">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 343, Column 34: character "&" is the first character of a delimiter but occurred as data
    <div class="boxtopom">Statistics & Page Rank</div>

    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 353, Column 23: document type does not allow element "style" here
    <style type="text/css">

    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 389, Column 5: document type does not allow element "br" here; assuming missing "li" start-tag
    <br/>
  • Error Line 390, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 389, Column 1: start tag was here
    <br/>
  • Error Line 402, Column 146: value of attribute "id" invalid: "1" cannot start a name
    …_central" style="list-style-type: none; padding: 0px; margin: 0;"><li id="102">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 405, Column 18: there is no attribute "bgcolor"
    <marquee bgcolor=#ffffff style="position: relative;" behavior="scroll" align="c…

    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 405, Column 18: an attribute value must be a literal unless it contains only name characters
    <marquee bgcolor=#ffffff style="position: relative;" behavior="scroll" align="c…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 405, Column 32: there is no attribute "style"
    <marquee bgcolor=#ffffff style="position: relative;" behavior="scroll" align="c…

    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 405, Column 63: there is no attribute "behavior"
    …ff style="position: relative;" behavior="scroll" align="center" direction="up" 

    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 405, Column 78: there is no attribute "align"
    …ff style="position: relative;" behavior="scroll" align="center" direction="up" 

    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 405, Column 97: there is no attribute "direction"
    …ff style="position: relative;" behavior="scroll" align="center" direction="up" 

    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 406, Column 14: there is no attribute "scrollamount"
    scrollamount="2" scrolldelay="1" onmouseover="this.stop()" onmouseout="this.sta…

    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 406, Column 30: there is no attribute "scrolldelay"
    scrollamount="2" scrolldelay="1" onmouseover="this.stop()" onmouseout="this.sta…

    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 406, Column 46: there is no attribute "onmouseover"
    …amount="2" scrolldelay="1" onmouseover="this.stop()" onmouseout="this.start()" 

    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 406, Column 71: there is no attribute "onmouseout"
    …amount="2" scrolldelay="1" onmouseover="this.stop()" onmouseout="this.start()" 

    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 407, Column 8: there is no attribute "height"
    height="150" width="500"><br>

    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 407, Column 20: there is no attribute "width"
    height="150" width="500"><br>

    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 407, Column 25: element "marquee" undefined
    height="150" width="500"><br>

    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 407, Column 30: end tag for "br" omitted, but OMITTAG NO was specified
    height="150" width="500"><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 407, Column 26: start tag was here
    height="150" width="500"><br>
  • Error Line 410, Column 7: document type does not allow element "table" here
    <table><tr>   <td>      <img class="thumb" src="http://open.thumbshots.org/imag…

    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 410, Column 139: required attribute "alt" not specified
    …thumbshots.org/image.pxf?url=http://www.shoppingdirectory.ws/online-shopping/">

    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 410, Column 140: end tag for "img" omitted, but OMITTAG NO was specified
    …thumbshots.org/image.pxf?url=http://www.shoppingdirectory.ws/online-shopping/">

    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 410, Column 25: start tag was here
    <table><tr>   <td>      <img class="thumb" src="http://open.thumbshots.org/imag…
  • Error Line 416, Column 723: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …nbsp;more</a><div style="clear: both;"></div></div></td></tr><tr><td colspan="…

    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 416, Column 735: end tag for "p" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 416, Column 319: start tag was here
    …Shopping Directory  </span>--><br/>   <p id="description6798">      <span id="…
  • Error Line 416, Column 735: end tag for "td" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 416, Column 15: start tag was here
    </div>   </td><td><a class="link" id="id_6798" href="http://www.shoppingdirecto…
  • Error Line 416, Column 735: end tag for "tr" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 410, Column 8: start tag was here
    <table><tr>   <td>      <img class="thumb" src="http://open.thumbshots.org/imag…
  • Error Line 416, Column 735: end tag for "table" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 410, Column 1: start tag was here
    <table><tr>   <td>      <img class="thumb" src="http://open.thumbshots.org/imag…
  • Error Line 416, Column 735: "table" not finished but containing element ended
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…
  • Error Line 416, Column 735: end tag for "table" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 409, Column 1: start tag was here
    <table>
  • Error Line 416, Column 740: end tag for element "td" which is not open
    … style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr></ta…

    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 416, Column 745: end tag for element "tr" which is not open
    …e="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr></table> …

    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 416, Column 783: end tag for element "table" which is not open
    …><tr><td colspan="2"></td></tr></table>               <table><tr>   <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 416, Column 923: required attribute "alt" not specified
    …="http://open.thumbshots.org/image.pxf?url=http://howtotakecareofaturtle.com/">

    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 416, Column 924: end tag for "img" omitted, but OMITTAG NO was specified
    …="http://open.thumbshots.org/image.pxf?url=http://howtotakecareofaturtle.com/">

    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 416, Column 823: start tag was here
    …              <table><tr>   <td>      <img class="thumb" src="http://open.thum…
  • Error Line 422, Column 805: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …nbsp;more</a><div style="clear: both;"></div></div></td></tr><tr><td colspan="…

    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 422, Column 817: end tag for "p" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 422, Column 281: start tag was here
    …>Turtle Care Guide  </span>--><br/>   <p id="description7048">      <span id="…
  • Error Line 422, Column 817: end tag for "td" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 422, Column 15: start tag was here
    </div>   </td><td><a class="link" id="id_7048" href="http://howtotakecareofatur…
  • Error Line 422, Column 817: end tag for "tr" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 416, Column 806: start tag was here
    …td></tr></table>               <table><tr>   <td>      <img class="thumb" src=…
  • Error Line 422, Column 817: end tag for "table" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 416, Column 799: start tag was here
    …="2"></td></tr></table>               <table><tr>   <td>      <img class="thum…
  • Error Line 422, Column 817: end tag for "marquee" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 405, Column 1: start tag was here
    <marquee bgcolor=#ffffff style="position: relative;" behavior="scroll" align="c…
  • Error Line 422, Column 817: end tag for "center" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 404, Column 1: start tag was here
    <center>
  • Error Line 422, Column 817: end tag for "li" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 402, Column 138: start tag was here
    …_central" style="list-style-type: none; padding: 0px; margin: 0;"><li id="102">
  • Error Line 422, Column 817: end tag for "ul" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 402, Column 56: start tag was here
    …script><div style="clear: both"></div><ul id="sortable_central" style="list-st…
  • Error Line 422, Column 822: end tag for element "td" which is not open
    … style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr></ta…

    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 422, Column 827: end tag for element "tr" which is not open
    …e="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr></table> …

    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 422, Column 831: document type does not allow element "tr" here; assuming missing "table" start-tag
    …lear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr></table>     …
  • Error Line 422, Column 1002: required attribute "alt" not specified
    …src="http://open.thumbshots.org/image.pxf?url=http://www.wondrouswallart.com/">

    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 422, Column 1003: end tag for "img" omitted, but OMITTAG NO was specified
    …src="http://open.thumbshots.org/image.pxf?url=http://www.wondrouswallart.com/">

    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 422, Column 905: start tag was here
    …              <table><tr>   <td>      <img class="thumb" src="http://open.thum…
  • Error Line 428, Column 852: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …nbsp;more</a><div style="clear: both;"></div></div></td></tr><tr><td colspan="…

    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 428, Column 864: end tag for "p" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 428, Column 341: start tag was here
    …stickers and decal  </span>--><br/>   <p id="description24749">      <span id=…
  • Error Line 428, Column 864: end tag for "td" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 428, Column 15: start tag was here
    </div>   </td><td><a class="link" id="id_24749" href="http://www.wondrouswallar…
  • Error Line 428, Column 864: end tag for "tr" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 422, Column 888: start tag was here
    …td></tr></table>               <table><tr>   <td>      <img class="thumb" src=…
  • Error Line 428, Column 864: end tag for "table" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 422, Column 881: start tag was here
    …="2"></td></tr></table>               <table><tr>   <td>      <img class="thum…
  • Error Line 428, Column 869: end tag for element "td" which is not open
    … style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr></ta…

    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 428, Column 874: end tag for element "tr" which is not open
    …e="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr></table> …

    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 428, Column 878: document type does not allow element "tr" here; assuming missing "table" start-tag
    …lear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr></table>     …
  • Error Line 428, Column 1072: required attribute "alt" not specified
    …hots.org/image.pxf?url=http://www.mitsubishi-motors.com.au/vehicles/cars/colt">

    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 428, Column 1073: end tag for "img" omitted, but OMITTAG NO was specified
    …hots.org/image.pxf?url=http://www.mitsubishi-motors.com.au/vehicles/cars/colt">

    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 428, Column 952: start tag was here
    …              <table><tr>   <td>      <img class="thumb" src="http://open.thum…
  • Error Line 434, Column 716: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …nbsp;more</a><div style="clear: both;"></div></div></td></tr><tr><td colspan="…

    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 434, Column 728: end tag for "p" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 434, Column 298: start tag was here
    …">Small Car Videos  </span>--><br/>   <p id="description1452">      <span id="…
  • Error Line 434, Column 728: end tag for "td" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 434, Column 15: start tag was here
    </div>   </td><td><a class="link" id="id_1452" href="http://www.mitsubishi-moto…
  • Error Line 434, Column 728: end tag for "tr" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 428, Column 935: start tag was here
    …td></tr></table>               <table><tr>   <td>      <img class="thumb" src=…
  • Error Line 434, Column 728: end tag for "table" omitted, but OMITTAG NO was specified
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr…

    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 428, Column 928: start tag was here
    …="2"></td></tr></table>               <table><tr>   <td>      <img class="thum…
  • Error Line 434, Column 733: end tag for element "td" which is not open
    … style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr></ta…

    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 434, Column 738: end tag for element "tr" which is not open
    …e="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr></table> …

    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 434, Column 742: document type does not allow element "tr" here; assuming missing "table" start-tag
    …lear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr></table>     …
  • Error Line 434, Column 916: required attribute "alt" not specified
    …="http://open.thumbshots.org/image.pxf?url=http://www.realtylinkdirectory.com">

    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 434, Column 917: end tag for "img" omitted, but OMITTAG NO was specified
    …="http://open.thumbshots.org/image.pxf?url=http://www.realtylinkdirectory.com">

    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 434, Column 816: start tag was here
    …              <table><tr>   <td>      <img class="thumb" src="http://open.thum…
  • Error Line 440, Column 366: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …7">      <span id="editdescrip_167"><p>Real estate agents and Brokers may subm…

    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 440, Column 802: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …nbsp;more</a><div style="clear: both;"></div></div></td></tr><tr><td colspan="…

    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 440, Column 814: end tag for element "div" which is not open
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></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 440, Column 819: end tag for "p" omitted, but OMITTAG NO was specified
    … style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr></ta…

    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 440, Column 308: start tag was here
    …te Agent Directory  </span>--><br/>   <p id="description167">      <span id="e…
  • Error Line 440, Column 988: required attribute "alt" not specified
    …ss="thumb" src="http://open.thumbshots.org/image.pxf?url=http://www.serif.com">

    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 440, Column 989: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="thumb" src="http://open.thumbshots.org/image.pxf?url=http://www.serif.com">

    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 440, Column 902: start tag was here
    …              <table><tr>   <td>      <img class="thumb" src="http://open.thum…
  • Error Line 446, Column 750: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …nbsp;more</a><div style="clear: both;"></div></div></td></tr><tr><td colspan="…

    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 446, Column 762: end tag for element "div" which is not open
    …><div style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></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 446, Column 767: end tag for "p" omitted, but OMITTAG NO was specified
    … style="clear: both;"></div></div></td></tr><tr><td colspan="2"></td></tr></ta…

    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 446, Column 273: start tag was here
    …eb Design Software  </span>--><br/>   <p id="description2393">      <span id="…
  • Error Line 446, Column 830: end tag for element "table" which is not open
    …/div></div></td></tr><tr><td colspan="2"></td></tr></table>            </table>

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

  • Error Line 448, Column 10: end tag for element "marquee" which is not open
    </marquee>

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

    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 450, Column 5: end tag for element "li" which is not open
    </li></div><div class="centerContainerB"></div></div><div class="rightContainer…

    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 450, Column 11: end tag for element "div" which is not open
    </li></div><div class="centerContainerB"></div></div><div class="rightContainer…

    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 450, Column 53: end tag for element "div" which is not open
    …li></div><div class="centerContainerB"></div></div><div class="rightContainer">

    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 452, Column 9: value of attribute "id" invalid: "2" cannot start a name
    <li id="204">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 453, Column 17: there is no attribute "href"
    <center><A href="http://www.alexa.com/siteinfo/http://addtodirectories.com" tar…

    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 453, Column 84: there is no attribute "target"
    …o/http://addtodirectories.com" target="_blank"><SCRIPT type='text/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 453, Column 92: element "A" undefined
    …/addtodirectories.com" target="_blank"><SCRIPT type='text/javascript' language…

    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 453, Column 106: there is no attribute "type"
    …ies.com" target="_blank"><SCRIPT type='text/javascript' 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 453, Column 133: there is no attribute "language"
    …CRIPT type='text/javascript' language='JavaScript' src='http://xslt.alexa.com/…

    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 453, Column 150: there is no attribute "src"
    …javascript' language='JavaScript' src='http://xslt.alexa.com/site_stats/js/t/b…

    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 453, Column 223: element "SCRIPT" undefined
    …site_stats/js/t/b?url=http://addtodirectories.com'></SCRIPT></A></center><br />

    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 455, Column 9: value of attribute "id" invalid: "2" cannot start a name
    <li id="209">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 477, Column 9: value of attribute "id" invalid: "2" cannot start a name
    <li id="207">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 499, Column 42: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="checkbox" name="rememberMe">&nbsp;&nbsp; Keep me logged 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 499, Column 1: start tag was here
    <input type="checkbox" name="rememberMe">&nbsp;&nbsp; Keep me logged in.
  • Error Line 513, Column 52: end tag for element "div" which is not open
    …lear: both; height: 30px;"></div></div><div id="footer-wrapper"><div id="three…

    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 513, Column 1343: cannot generate system identifier for general entity "tid1"
    …filiates.arvixe.com/track.php?id=3073&tid1=footer">Our Hosting Provider</a></l…

    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 513, Column 1343: general entity "tid1" not defined and no default entity
    …filiates.arvixe.com/track.php?id=3073&tid1=footer">Our Hosting Provider</a></l…

    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 513, Column 1347: reference not terminated by REFC delimiter
    …ates.arvixe.com/track.php?id=3073&tid1=footer">Our Hosting Provider</a></li><l…

    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 513, Column 1347: reference to external entity in attribute value
    …ates.arvixe.com/track.php?id=3073&tid1=footer">Our Hosting Provider</a></li><l…

    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 513, Column 1347: reference to entity "tid1" for which no system identifier could be generated
    …ates.arvixe.com/track.php?id=3073&tid1=footer">Our Hosting Provider</a></li><l…

    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 513, Column 1342: entity was defined here
    …ffiliates.arvixe.com/track.php?id=3073&tid1=footer">Our Hosting Provider</a></…

Visitor Analysis

Daily Visitor
  • 3.967 visits
Daily Visitor