StarCelebs.com free nude celebrity pics and galleries featuring star actresses, models, singers, and athletes. ...

starcelebs.com
  • Domain Name
    starcelebs.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #12407
  • Page Size
    131.9 KB
  • Ip Address
    64.6.101.113
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 9 JPG, 0 PNG

Website Meta Analysis

  • Title
    Star Celebs - Nude celebrity pics of actresses, models, singers, and athletes.
  • Meta Keyword
    Starcelebs, starcelebs.com, star celebs, nude celebs, nude celebrity pics, celeb pics, celeb galleries, free nude celebs
  • Meta Description
    StarCelebs.com free nude celebrity pics and galleries featuring star actresses, models, singers, and athletes.

Technical Analysis

  • Webserver
    Apache/2
  • Ip Address
    64.6.101.113
  • Domain Age
    11 Years, 8 Months, 13 days.
  • Javascript Library
    yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Mon, 09 Sep 2013 15:09:41 GMT
  • server: Apache/2
  • last-modified: Mon, 09 Sep 2013 14:53:50 GMT
  • etag: "1f9a7ed-2007e-4e5f48e5bbb80"
  • accept-ranges: bytes
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 28480
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domain Privacy Group
70 Blanchard Road
Burlington, MA 01803
US

Domain name: STARCELEBS.COM

Administrative Contact:
Privacy Group, Domain email
70 Blanchard Road
Burlington, MA 01803
US
+1.6027165339
Technical Contact:
Privacy Group, Domain email
70 Blanchard Road
Burlington, MA 01803
US
+1.6027165339

Registration Service Provider:
MyDomain, email
+1.8004057875
This company may be contacted for domain login/passwords,
DNS/Nameserver changes, and general domain support questions.

Registrar of Record: Domain.com
Record last updated on 13-Aug-2012.
Record expires on 28-Dec-2013.
Record created on 28-Dec-2001.

Domain servers in listed order:
NS1.AMERINOC.COM
NS2.AMERINOC.COM

Domain status: clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited

This domain's privacy is protected by domainprivacygroup.com. To reach the domain contacts, please go to http://www.domainprivacygroup.com and follow the instructions.

DNS Analysis


DNS servers
ns1.amerinoc.com [216.17.96.210]
ns2.amerinoc.com [216.17.104.103]


DNS Records

Answer records
starcelebs.com SOA
server: ns1.amerinoc.com
email: root@starcelebs.com
serial: 2010101701
refresh: 14400
retry: 3600
expire: 1209600
minimum ttl: 86400
14400s
starcelebs.com NS  ns1.amerinoc.com 14400s
starcelebs.com NS  ns2.amerinoc.com 14400s
starcelebs.com A 64.6.101.113 14400s
starcelebs.com MX
preference: 10
exchange: mail.starcelebs.com
14400s

Authority records

Additional records
ns1.amerinoc.com A 216.17.96.210 14400s
ns2.amerinoc.com A 216.17.104.103 14400s
mail.starcelebs.com A 64.6.101.113 14400s

IP 64.6.101.113 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    San Diego
  • Continent Code
    92117
  • Latitude
    858
  • Longitude
    825
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 64.6.101.113"
    #
    # Use "?" to get help.
    #

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

    NetRange: 64.6.96.0 - 64.6.111.255
    CIDR: 64.6.96.0/20
    OriginAS: AS30266
    NetName: A1COLO
    NetHandle: NET-64-6-96-0-1
    Parent: NET-64-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2008-04-10
    Updated: 2008-12-04
    Ref: http://whois.arin.net/rest/net/NET-64-6-96-0-1

    OrgName: A1COLO.COM
    OrgId: A1COL
    Address: PMB #241 3089 - C CLAIREMONT DR.
    City: San Diego
    StateProv: CA
    PostalCode: 92117
    Country: US
    RegDate: 2004-08-13
    Updated: 2011-09-24
    Ref: http://whois.arin.net/rest/org/A1COL

    OrgTechHandle: TECHA4-ARIN
    OrgTechName: Tech Admin
    OrgTechPhone: +1-877-805-6542
    OrgTechEmail: poc@a1colo.com
    OrgTechRef: http://whois.arin.net/rest/poc/TECHA4-ARIN

    OrgAbuseHandle: TECHA4-ARIN
    OrgAbuseName: Tech Admin
    OrgAbusePhone: +1-877-805-6542
    OrgAbuseEmail: poc@a1colo.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/TECHA4-ARIN

    RTechHandle: TECHA4-ARIN
    RTechName: Tech Admin
    RTechPhone: +1-877-805-6542
    RTechEmail: poc@a1colo.com
    RTechRef: http://whois.arin.net/rest/poc/TECHA4-ARIN

    RNOCHandle: TECHA4-ARIN
    RNOCName: Tech Admin
    RNOCPhone: +1-877-805-6542
    RNOCEmail: poc@a1colo.com
    RNOCRef: http://whois.arin.net/rest/poc/TECHA4-ARIN

    RAbuseHandle: TECHA4-ARIN
    RAbuseName: Tech Admin
    RAbusePhone: +1-877-805-6542
    RAbuseEmail: poc@a1colo.com
    RAbuseRef: http://whois.arin.net/rest/poc/TECHA4-ARIN

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 66 Errors
  • 11 Warnings
Ratio Text/Html
  • 0.7395698367452708
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Warning Line 85, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="hucOZQ_0u54yy5kQfhqKCjREnysFhFyksM3bmwistEk" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 99, Column 7: end tag for element "HEAD" which is not open
    </head>

    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 100, Column 86: document type does not allow element "BODY" here
    …gcolor="#BBDDFF" text="#000000" link="#000000" vlink="#000000" alink="#000000">

    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 102, Column 27: there is no attribute "HEIGHT"
    <table width="690" height="140" cellspacing="0" cellpadding="0" border="0">

    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 103, Column 14: there is no attribute "WITH"
    <tr><td with="490" valign="top" align="left">

    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 106, Column 31: value of attribute "VALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "BASELINE"
    <td width="200" valign="center" align="left">

    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.

  • Warning Line 111, Column 68: cannot generate system identifier for general entity "prog"
    …-tracking01.com/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="win…

    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 111, Column 68: general entity "prog" not defined and no default entity
    …-tracking01.com/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="win…

    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.

  • Error Line 111, Column 72: reference to entity "prog" for which no system identifier could be generated
    …cking01.com/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="window.…

    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 111, Column 67: entity was defined here
    …t-tracking01.com/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="wi…
  • Warning Line 111, Column 75: cannot generate system identifier for general entity "site"
    …ng01.com/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="window.sta…

    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 111, Column 75: general entity "site" not defined and no default entity
    …ng01.com/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="window.sta…

    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.

  • Error Line 111, Column 79: reference to entity "site" for which no system identifier could be generated
    ….com/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="window.status=…

    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 111, Column 74: entity was defined here
    …ing01.com/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="window.st…
  • Warning Line 111, Column 83: cannot generate system identifier for general entity "skin"
    …/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="window.status='htt…

    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 111, Column 83: general entity "skin" not defined and no default entity
    …/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="window.status='htt…

    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.

  • Error Line 111, Column 87: reference to entity "skin" for which no system identifier could be generated
    …/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="window.status='http://…

    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 111, Column 82: entity was defined here
    …m/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="window.status='ht…
  • Warning Line 115, Column 74: cannot generate system identifier for general entity "PA"
    …bill.com/cgi-bin/clicks.cgi?CA=906535&PA=593320" onMouseOver="window.status='h…

    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 115, Column 74: general entity "PA" not defined and no default entity
    …bill.com/cgi-bin/clicks.cgi?CA=906535&PA=593320" onMouseOver="window.status='h…

    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.

  • Error Line 115, Column 76: reference to entity "PA" for which no system identifier could be generated
    …ll.com/cgi-bin/clicks.cgi?CA=906535&PA=593320" onMouseOver="window.status='htt…

    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 115, Column 73: entity was defined here
    …cbill.com/cgi-bin/clicks.cgi?CA=906535&PA=593320" onMouseOver="window.status='…
  • Error Line 122, Column 210: required attribute "ALT" not specified
    …><img src="/logos/realteeniegirls.jpg" width="732" height="366" border="0"></a>

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

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

  • Error Line 126, Column 90: there is no attribute "BORDERCOLOR"
    …ellpadding="0" border="1" bordercolor="gray" bordercolordark="gray" bordercolo…

    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 126, Column 113: there is no attribute "BORDERCOLORDARK"
    …1" bordercolor="gray" bordercolordark="gray" bordercolorlight="gray" bgcolor="…

    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 126, Column 137: there is no attribute "BORDERCOLORLIGHT"
    …rcolor="gray" bordercolordark="gray" bordercolorlight="gray" bgcolor="#BBDDFF">

    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 128, Column 31: value of attribute "VALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "BASELINE"
    <td width="732" valign="center" align="center" bgcolor="#BBDDFF" height="25">

    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 132, Column 19: value of attribute "VALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "BASELINE"
    <td valign="center" align="center" width="732" height="135">

    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 182, Column 64: literal is missing closing delimiter
    <table class="thumbs" width="700" cellspacing="0" cellpadding="0' border="0">

    Did you forget to close a (double) quote mark?

  • Error Line 182, Column 76: character data is not allowed here
    <table class="thumbs" width="700" cellspacing="0" cellpadding="0' border="0">

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 186, Column 46: value of attribute "VALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "BASELINE"
    <td width="140" align="center" valign="center">

    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 187, Column 144: an attribute specification must start with a name or name token
    …jpg" width="100" height="100" border= 1" bordercolor="white"></a><br>Katy Perry

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 190, Column 46: value of attribute "VALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "BASELINE"
    <td width="140" align="center" valign="center">

    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 191, Column 182: an attribute specification must start with a name or name token
    …pg" width="100" height="100" border= 1" bordercolor="white"></a><br>Olivia Mun…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 194, Column 46: value of attribute "VALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "BASELINE"
    <td width="140" align="center" valign="center">

    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 195, Column 175: there is no attribute "BORDERCOLOR"
    …th="100" height="100" border="1" bordercolor="white"></a><br>Emmanuelle Chriqui

    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 195, Column 182: required attribute "ALT" not specified
    …th="100" height="100" border="1" bordercolor="white"></a><br>Emmanuelle Chriqui

    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 197, Column 46: value of attribute "VALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "BASELINE"
    <td width="140" align="center" valign="center">

    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 198, Column 191: required attribute "ALT" not specified
    …width="100" height="100" border="1" bordercolor="white"></a><br>Karissa Shannon

    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 201, Column 46: value of attribute "VALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "BASELINE"
    <td width="140" align="center" valign="center">

    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 202, Column 203: an attribute specification must start with a name or name token
    …pg" width="100" height="100" border= 1" bordercolor="white"></a><br>Lindsay Lo…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 214, Column 72: end tag for "B" omitted, but its declaration does not permit this
    …or="#000000"><b>Site of the Day:</font></b> &nbsp;<a href="http://secure.reali…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 214, Column 47: start tag was here
    …ze="2" face="verdana" color="#000000"><b>Site of the Day:</font></b> &nbsp;<a …
  • Error Line 214, Column 76: end tag for element "B" which is not open
    …#000000"><b>Site of the Day:</font></b> &nbsp;<a href="http://secure.realityst…

    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 215, Column 5: end tag for "B" omitted, but its declaration does not permit this
    </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 214, Column 346: start tag was here
    …s</b></font></a> <font size="2" face="verdana" color="#000000"><b>[$1.00 Trial]
  • Error Line 215, Column 5: end tag for "FONT" omitted, but its declaration does not permit this
    </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 214, Column 300: start tag was here
    …>Reality Star Scandals</b></font></a> <font size="2" face="verdana" color="#00…
  • Error Line 232, Column 20: value of attribute "ALIGN" must be a single token
    <tr><td align="left valign="top">

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

  • Error Line 232, Column 27: character "=" is not allowed in the value of attribute "ALIGN"
    <tr><td align="left valign="top">

    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 232, Column 28: value of attribute "ALIGN" cannot be "LEFT VALIGN="; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
    <tr><td align="left valign="top">

    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 232, Column 32: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    <tr><td align="left valign="top">

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 372, Column 20: value of attribute "ALIGN" must be a single token
    <tr><td align="left valign="top">

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

  • Error Line 372, Column 27: character "=" is not allowed in the value of attribute "ALIGN"
    <tr><td align="left valign="top">

    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 372, Column 28: value of attribute "ALIGN" cannot be "LEFT VALIGN="; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
    <tr><td align="left valign="top">

    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 372, Column 32: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    <tr><td align="left valign="top">

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 441, Column 20: value of attribute "ALIGN" must be a single token
    <tr><td align="left valign="top">

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

  • Error Line 441, Column 27: character "=" is not allowed in the value of attribute "ALIGN"
    <tr><td align="left valign="top">

    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 441, Column 28: value of attribute "ALIGN" cannot be "LEFT VALIGN="; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
    <tr><td align="left valign="top">

    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 441, Column 32: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    <tr><td align="left valign="top">

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 456, Column 20: value of attribute "ALIGN" must be a single token
    <tr><td align="left valign="top">

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

  • Error Line 456, Column 27: character "=" is not allowed in the value of attribute "ALIGN"
    <tr><td align="left valign="top">

    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 456, Column 28: value of attribute "ALIGN" cannot be "LEFT VALIGN="; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
    <tr><td align="left valign="top">

    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 456, Column 32: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    <tr><td align="left valign="top">

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 458, Column 77: reference to entity "prog" for which no system identifier could be generated
    …cking01.com/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="window.…

    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 111, Column 67: entity was defined here
    …t-tracking01.com/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="wi…
  • Error Line 458, Column 84: reference to entity "site" for which no system identifier could be generated
    ….com/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="window.status=…

    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 111, Column 74: entity was defined here
    …ing01.com/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="window.st…
  • Error Line 458, Column 92: reference to entity "skin" for which no system identifier could be generated
    …/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="window.status='http://…

    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 111, Column 82: entity was defined here
    …m/aff/ep.php?act=225051&prog=1&site=90&skin=ht" onMouseOver="window.status='ht…
  • Warning Line 460, Column 58: cannot generate system identifier for general entity "clc"
    …href="http://exploitedfame.com/?cds=1&clc=PRUwBIPndhnPVc9OzE-orw" onMouseOver=…

    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 460, Column 58: general entity "clc" not defined and no default entity
    …href="http://exploitedfame.com/?cds=1&clc=PRUwBIPndhnPVc9OzE-orw" onMouseOver=…

    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.

  • Error Line 460, Column 61: reference to entity "clc" for which no system identifier could be generated
    …f="http://exploitedfame.com/?cds=1&clc=PRUwBIPndhnPVc9OzE-orw" onMouseOver="wi…

    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 460, Column 57: entity was defined here
    … href="http://exploitedfame.com/?cds=1&clc=PRUwBIPndhnPVc9OzE-orw" onMouseOver…
  • Error Line 466, Column 81: reference to entity "PA" for which no system identifier could be generated
    …ll.com/cgi-bin/clicks.cgi?CA=906535&PA=593320" onMouseOver="window.status='htt…

    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 115, Column 73: entity was defined here
    …cbill.com/cgi-bin/clicks.cgi?CA=906535&PA=593320" onMouseOver="window.status='…
  • Error Line 474, Column 210: required attribute "ALT" not specified
    …><img src="/logos/whitegfvertical.jpg" width="160" height="600" border="1"></a>

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

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

  • Error Line 481, Column 211: required attribute "ALT" not specified
    …"><img src="/logos/mrskinleftside.jpg" width="160" height="600" border="1"></a>

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

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

  • Error Line 488, Column 230: required attribute "ALT" not specified
    …img src="/logos/bannedcelebsvert1.gif" width="120" height="600" border="1"></a>

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

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

  • Error Line 495, Column 240: required attribute "ALT" not specified
    …<img src="/logos/homemadeleftside.gif" width="120" height="600" border="1"></a>

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

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

  • Error Line 2115, Column 4: end tag for element "P" which is not open
    </p>

    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 2121, Column 232: duplicate specification of attribute "TARGET"
    …xy-photos.net/" target="_self" target="_self"><font face="verdana" size="4" co…

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

  • Error Line 2121, Column 443: duplicate specification of attribute "TARGET"
    …ot Nude Celebs" target="_self" target="_self"><font face="verdana" size="4" co…

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

  • Error Line 2121, Column 622: duplicate specification of attribute "TARGET"
    …ebrity-tgp.com" target="_self" target="_self"><font face="verdana" size="4" co…

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

  • Error Line 2122, Column 58: duplicate specification of attribute "TARGET"
    ….rudespace.com" target="_self" target="_self"><font face="verdana" size="4" co…

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

  • Error Line 2122, Column 232: duplicate specification of attribute "TARGET"
    …te/o.cgi?id=54" target="_self" target="_self"><font face="verdana" size="4" co…

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

  • Error Line 2122, Column 413: duplicate specification of attribute "TARGET"
    …edirectory.com" target="_self" target="_self"><font face="verdana" size="4" co…

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

  • Error Line 2139, Column 7: end tag for "CENTER" omitted, but its declaration does not permit this
    </body>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 101, Column 1: start tag was here
    <center>

Visitor Analysis

Daily Visitor
  • 17.150 visits
Daily Visitor