DONTBESCARED In Before... Freaky Tales Tattoos And... Sexy Black... Breeyana and... Wet And Ready CITY FREAKS See All SmashAdams Rod Jebediah SwampNigga raw2nd VineXXX Ifusker JoeAqua See All VISIT OTHER PARTS OF OUR ...

shesfreaky.com
  • Domain Name
    shesfreaky.com
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #56059
  • Page Size
    90.5 KB
  • Ip Address
    64.6.108.79
  • Heading
    H1: 0, H2: 6, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    7 GIF, 77 JPG, 17 PNG

Website Meta Analysis

  • Title
    Shes Freaky | Free Black Amateur Porn Videos And Pics
  • Meta Keyword
  • Meta Description
    DONTBESCARED In Before... Freaky Tales Tattoos And... Sexy Black... Breeyana and... Wet And Ready CITY FREAKS See All SmashAdams Rod Jebediah SwampNigga raw2nd VineXXX Ifusker JoeAqua See All VISIT OTHER PARTS OF OUR NETWORK: Wall Of Freaks ...

Technical Analysis

  • Webserver
    Apache/2
  • Ip Address
    64.6.108.79
  • Domain Age
    1 Years, 9 Months, 21 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 07 Sep 2013 01:46:32 GMT
  • server: Apache/2
  • x-powered-by: PHP/5.3.21
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 11449
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: shesfreaky.com

Registrant Contact:
WhoisGuard
WhoisGuard Protected ()

Fax:
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Administrative Contact:
WhoisGuard
WhoisGuard Protected ( email )
+1.6613102107
Fax: +1.6613102107
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Technical Contact:
WhoisGuard
WhoisGuard Protected ( email )
+1.6613102107
Fax: +1.6613102107
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Status: Locked

Name Servers:
ns1.amerinoc.com
ns2.amerinoc.com

Creation date: 25 Nov 2011 08:24:00
Expiration date: 25 Nov 2013 00:24:00

DNS Analysis


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


DNS Records

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

Authority records

Additional records
mail.shesfreaky.com A 64.6.108.79 14400s
ns1.amerinoc.com A 216.17.96.210 14400s
ns2.amerinoc.com A 216.17.104.103 14400s

IP 64.6.108.79 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 23 Errors
  • 25 Warnings
Ratio Text/Html
  • 0.6909377428546757
Message Error
  • Error Line 16, Column 180: end tag for "meta" omitted, but OMITTAG NO was specified
    …omegrown videos and pictures. 100% free videos, Ebony Porn updated every day.">

    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 16, Column 1: start tag was here
    <meta name="description" content="ShesFreaky is the #1 Black Amateur Porn Tube …
  • Error Line 193, Column 62: end tag for "input" omitted, but OMITTAG NO was specified
            <input type="submit" value="" class="search_button" >

    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 193, Column 9: start tag was here
            <input type="submit" value="" class="search_button" >
  • Error Line 362, Column 150: required attribute "alt" not specified
    …="_blank"><img src="http://www.shesfreaky.com/images/banners/cattop/2.gif"></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 362, Column 154: end tag for "img" omitted, but OMITTAG NO was specified
    …="_blank"><img src="http://www.shesfreaky.com/images/banners/cattop/2.gif"></a>

    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 362, Column 86: start tag was here
    …rack/NjMwOjI6NDI,10/" target="_blank"><img src="http://www.shesfreaky.com/imag…
  • Error Line 372, Column 150: required attribute "alt" not specified
    …="_blank"><img src="http://www.shesfreaky.com/images/banners/cattop/2.jpg"></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 372, Column 154: end tag for "img" omitted, but OMITTAG NO was specified
    …="_blank"><img src="http://www.shesfreaky.com/images/banners/cattop/2.jpg"></a>

    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 372, Column 86: start tag was here
    …rack/NjMwOjI6NDI,10/" target="_blank"><img src="http://www.shesfreaky.com/imag…
  • Error Line 382, Column 150: required attribute "alt" not specified
    …="_blank"><img src="http://www.shesfreaky.com/images/banners/cattop/3.jpg"></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 382, Column 154: end tag for "img" omitted, but OMITTAG NO was specified
    …="_blank"><img src="http://www.shesfreaky.com/images/banners/cattop/3.jpg"></a>

    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 382, Column 86: start tag was here
    …rack/NjMwOjI6NDI,10/" target="_blank"><img src="http://www.shesfreaky.com/imag…
  • Error Line 392, Column 150: required attribute "alt" not specified
    …="_blank"><img src="http://www.shesfreaky.com/images/banners/cattop/4.jpg"></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 392, Column 154: end tag for "img" omitted, but OMITTAG NO was specified
    …="_blank"><img src="http://www.shesfreaky.com/images/banners/cattop/4.jpg"></a>

    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 392, Column 86: start tag was here
    …rack/NjMwOjI6NDI,10/" target="_blank"><img src="http://www.shesfreaky.com/imag…
  • Error Line 402, Column 150: required attribute "alt" not specified
    …="_blank"><img src="http://www.shesfreaky.com/images/banners/cattop/5.jpg"></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 402, Column 154: end tag for "img" omitted, but OMITTAG NO was specified
    …="_blank"><img src="http://www.shesfreaky.com/images/banners/cattop/5.jpg"></a>

    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 86: start tag was here
    …rack/NjMwOjI6NDI,10/" target="_blank"><img src="http://www.shesfreaky.com/imag…
  • Error Line 412, Column 150: required attribute "alt" not specified
    …="_blank"><img src="http://www.shesfreaky.com/images/banners/cattop/6.jpg"></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 412, Column 154: end tag for "img" omitted, but OMITTAG NO was specified
    …="_blank"><img src="http://www.shesfreaky.com/images/banners/cattop/6.jpg"></a>

    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 412, Column 86: start tag was here
    …rack/NjMwOjI6NDI,10/" target="_blank"><img src="http://www.shesfreaky.com/imag…
  • Error Line 509, Column 454: value of attribute "id" invalid: "9" cannot start a name
    …22/7430/main.jpg');" alt="Close Up Wet Pussy"  id="9YQP42OmMuO" /> </a>  </div>

    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 575, Column 465: value of attribute "id" invalid: "5" cannot start a name
    …/main.jpg');" alt="USG: Ms. Apple Pack pt. 1"  id="5SXOL4qmyjQ" /> </a>  </div>

    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 707, Column 444: value of attribute "id" invalid: "1" cannot start a name
    …os/0347/7394/main.jpg');" alt="booty shaking"  id="1c7EgJ5s6mh" /> </a>  </div>

    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 740, Column 464: value of attribute "id" invalid: "9" cannot start a name
    …93/main.jpg');" alt="Stunning Latina Camming"  id="9Pmta9dG0Es" /> </a>  </div>

    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 806, Column 470: value of attribute "id" invalid: "3" cannot start a name
    …main.jpg');" alt="Getten Freaky n the office"  id="3hiFjmWgoO6" /> </a>  </div>

    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 971, Column 444: value of attribute "id" invalid: "6" cannot start a name
    …os/0397/7370/main.jpg');" alt="Anal Assassin"  id="6tLt5wSnave" /> </a>  </div>

    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 1367, Column 460: value of attribute "id" invalid: "3" cannot start a name
    …7279/main.jpg');" alt="Thick Butt Black Milf"  id="38npgov5fLT" /> </a>  </div>

    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 1499, Column 436: value of attribute "id" invalid: "7" cannot start a name
    …videos/0537/7249/main.jpg');" alt="Sexy Slim"  id="7U10aeSIvqI" /> </a>  </div>

    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 1664, Column 450: value of attribute "id" invalid: "4" cannot start a name
    …0912/7227/main.jpg');" alt="making her cream"  id="4yas9i76Mw2" /> </a>  </div>

    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 1697, Column 463: value of attribute "id" invalid: "1" cannot start a name
    …05/main.jpg');" alt="Sweetsin From USG pt. 1"  id="1r1rc99w517" /> </a>  </div>

    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 1895, Column 457: value of attribute "id" invalid: "2" cannot start a name
    …/7155/main.jpg');" alt="Big Clit ebony Pt. 2"  id="2vajUe0d7nh" /> </a>  </div>

    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 2007, Column 6: element "left" undefined
    <left><a href="http://join.ebonyrevenge.com/track/NjMwOjI6NDI,10/" target="_bla…

    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 2007, Column 148: required attribute "alt" not specified
    …k"><img src="http://www.shesfreaky.com/images/banners/200x1000.gif"></a></left>

    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 2007, Column 152: end tag for "img" omitted, but OMITTAG NO was specified
    …k"><img src="http://www.shesfreaky.com/images/banners/200x1000.gif"></a></left>

    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 2007, Column 84: start tag was here
    …rack/NjMwOjI6NDI,10/" target="_blank"><img src="http://www.shesfreaky.com/imag…
  • Error Line 2011, Column 6: element "left" undefined
    <left><a href="http://www.blackgfs.com/main.htm?id=comein" target="_blank"><img…

    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 2011, Column 139: required attribute "alt" not specified
    …nk"><img src="http://www.shesfreaky.com/images/banners/sidebar.jpg"></a></left>

    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 2011, Column 143: end tag for "img" omitted, but OMITTAG NO was specified
    …nk"><img src="http://www.shesfreaky.com/images/banners/sidebar.jpg"></a></left>

    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 2011, Column 76: start tag was here
    …m/main.htm?id=comein" target="_blank"><img src="http://www.shesfreaky.com/imag…
  • Warning Line 2012, Column 98: cannot generate system identifier for general entity "flip"
    …mad/imad-v1.2.js?domain=streamate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=35…

    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 2012, Column 98: general entity "flip" not defined and no default entity
    …mad/imad-v1.2.js?domain=streamate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=35…

    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 2012, Column 102: reference not terminated by REFC delimiter
    …imad-v1.2.js?domain=streamate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&mu…

    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 2012, Column 102: reference to external entity in attribute value
    …imad-v1.2.js?domain=streamate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&mu…

    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 2012, Column 102: reference to entity "flip" for which no system identifier could be generated
    …imad-v1.2.js?domain=streamate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&mu…

    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 2012, Column 97: entity was defined here
    …imad/imad-v1.2.js?domain=streamate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=3…
  • Warning Line 2012, Column 105: cannot generate system identifier for general entity "AFNO"
    …d-v1.2.js?domain=streamate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&muted…

    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 2012, Column 105: general entity "AFNO" not defined and no default entity
    …d-v1.2.js?domain=streamate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&muted…

    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 2012, Column 109: reference not terminated by REFC delimiter
    ….2.js?domain=streamate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&muted=1" …

    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 2012, Column 109: reference to external entity in attribute value
    ….2.js?domain=streamate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&muted=1" …

    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 2012, Column 109: reference to entity "AFNO" for which no system identifier could be generated
    ….2.js?domain=streamate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&muted=1" …

    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 2012, Column 104: entity was defined here
    …ad-v1.2.js?domain=streamate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&mute…
  • Warning Line 2012, Column 128: cannot generate system identifier for general entity "UHNSMTY"
    …ate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&muted=1" type="text/javascri…

    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 2012, Column 128: general entity "UHNSMTY" not defined and no default entity
    …ate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&muted=1" type="text/javascri…

    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 2012, Column 135: reference not terminated by REFC delimiter
    …&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&muted=1" type="text/javascript" cha…

    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 2012, Column 135: reference to external entity in attribute value
    …&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&muted=1" type="text/javascript" cha…

    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 2012, Column 135: reference to entity "UHNSMTY" for which no system identifier could be generated
    …&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&muted=1" type="text/javascript" cha…

    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 2012, Column 127: entity was defined here
    …mate.com&flip=0&AFNO=1-0-596045-338402&UHNSMTY=354&muted=1" type="text/javascr…
  • Warning Line 2012, Column 140: cannot generate system identifier for general entity "muted"
    …=0&AFNO=1-0-596045-338402&UHNSMTY=354&muted=1" type="text/javascript" charset=…

    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 2012, Column 140: general entity "muted" not defined and no default entity
    …=0&AFNO=1-0-596045-338402&UHNSMTY=354&muted=1" type="text/javascript" charset=…

    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 2012, Column 145: reference not terminated by REFC delimiter
    …NO=1-0-596045-338402&UHNSMTY=354&muted=1" type="text/javascript" charset="utf-…

    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 2012, Column 145: reference to external entity in attribute value
    …NO=1-0-596045-338402&UHNSMTY=354&muted=1" type="text/javascript" charset="utf-…

    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 2012, Column 145: reference to entity "muted" for which no system identifier could be generated
    …NO=1-0-596045-338402&UHNSMTY=354&muted=1" type="text/javascript" charset="utf-…

    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 2012, Column 139: entity was defined here
    …p=0&AFNO=1-0-596045-338402&UHNSMTY=354&muted=1" type="text/javascript" charset…
  • Error Line 2072, Column 96: required attribute "alt" not specified
    …ltft"><img src="http://www.shesfreaky.com/stp/images/custom/redleft.png"></div>

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

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

  • Error Line 2072, Column 102: end tag for "img" omitted, but OMITTAG NO was specified
    …ltft"><img src="http://www.shesfreaky.com/stp/images/custom/redleft.png"></div>

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

  • Info Line 2072, Column 30: start tag was here
          <div class="floatltft"><img src="http://www.shesfreaky.com/stp/images/cus…
  • Error Line 2100, Column 94: required attribute "alt" not specified
    …atltft"><img src="http://www.shesfreaky.com/stp/images/custom/right.png"></div>

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

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

  • Error Line 2100, Column 100: end tag for "img" omitted, but OMITTAG NO was specified
    …atltft"><img src="http://www.shesfreaky.com/stp/images/custom/right.png"></div>

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

  • Info Line 2100, Column 30: start tag was here
          <div class="floatltft"><img src="http://www.shesfreaky.com/stp/images/cus…
  • Error Line 2343, Column 94: required attribute "alt" not specified
    …ltft"><img src="http://www.shesfreaky.com/stp/images/custom/redleft.png"></div>

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

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

  • Error Line 2343, Column 100: end tag for "img" omitted, but OMITTAG NO was specified
    …ltft"><img src="http://www.shesfreaky.com/stp/images/custom/redleft.png"></div>

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

  • Info Line 2343, Column 28: start tag was here
        <div class="floatltft"><img src="http://www.shesfreaky.com/stp/images/custo…
  • Error Line 2361, Column 92: required attribute "alt" not specified
    …atltft"><img src="http://www.shesfreaky.com/stp/images/custom/right.png"></div>

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

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

  • Error Line 2361, Column 98: end tag for "img" omitted, but OMITTAG NO was specified
    …atltft"><img src="http://www.shesfreaky.com/stp/images/custom/right.png"></div>

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

  • Info Line 2361, Column 28: start tag was here
        <div class="floatltft"><img src="http://www.shesfreaky.com/stp/images/custo…

Visitor Analysis

Daily Visitor
  • 3.383 visits