Get the best prices on the top electronics, appliances, computers, TV’s, and furniture from leading manufacturers. Our lease to own and affordable options make it easy. ...

aarons.com
  • Domain Name
    aarons.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #31888
  • Page Size
    50.5 KB
  • Ip Address
    12.177.80.16
  • Heading
    H1: 1, H2: 9, H3: 6, H4: 1, H5: 0, H6: 0
  • Images
    1 GIF, 9 JPG, 24 PNG

Website Meta Analysis

  • Title
    Lease to Own Furniture, Computers, Electronics, Appliances | Aaron’s
  • Meta Keyword
    aarons
  • Meta Description
    Get the best prices on the top electronics, appliances, computers, TV’s, and furniture from leading manufacturers. Our lease to own and affordable options make it easy.

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    12.177.80.16
  • Domain Age
    16 Years, 8 Months, 25 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • pragma: no-cache
  • content-length: 54615
  • content-type: text/html; charset=utf-8
  • expires: Fri, 28 Jun 2013 13:08:06 GMT
  • server: Microsoft-IIS/7.5
  • x-aspnet-version: 2.0.50727
  • x-powered-by: ASP.NET
  • date: Fri, 28 Jun 2013 13:08:06 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Landers, Lee
Aaron's, Inc,
1015 Cobb Place Blvd.
Kennesaw, GA 30144
US

Domain Name: AARONS.COM



Administrative Contact, Technical Contact:
Registrant, Domain email
Aaron's, Inc.
1015 Cobb Place Blvd.
Kennesaw, GA 30144
US
678-402-3000

Record expires on 29-Oct-2018.
Record created on 30-Oct-1996.
Database last updated on 26-Jul-2012 16:13:17 EDT.

Domain servers in listed order:

NS14.WORLDNIC.COM 206.188.198.7
NS13.WORLDNIC.COM 205.178.190.7

DNS Analysis


DNS servers
ns14.worldnic.com
ns13.worldnic.com


DNS Records

Answer records
aarons.com NS  ns13.worldnic.com 7200s
aarons.com MX
preference: 10
exchange: d14812a.ess.barracudanetworks.com
7200s
aarons.com A 12.177.80.9 7200s
aarons.com SOA
server: NS13.WORLDNIC.COM
email: namehost@WORLDNIC.COM
serial: 112121715
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
7200s
aarons.com MX
preference: 30
exchange: d14812b.ess.barracudanetworks.com
7200s
aarons.com NS  ns14.worldnic.com 7200s

Authority records

Additional records

IP 12.177.80.16 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 36 Errors
  • 10 Warnings
Ratio Text/Html
  • 0.6369804755461048
Message Error
  • Error Line 208, Column 365: end tag for "img" omitted, but OMITTAG NO was specified
    …="border:none;" src="/skins/Skin_1/images/change-location.png"></a><br /><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 208, Column 264: start tag was here
    …ationFinderPopUpChangeLocationButton"><img alt="Change my location" style="bor…
  • Error Line 237, Column 41: "mporgnav" is not a member of a group specified for any attribute
    …                          <a mporgnav href='http://espanol.aarons.com/' onclic…
  • Error Line 250, Column 90: there is no attribute "addthis:userid"
    …      <a class="addthis_button_facebook_follow" addthis:userid="aaronsinc"></a>

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

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

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

  • Error Line 440, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
    …/images/promos/LOveBedrm.jpg" alt="Bedroom Group" width="906" height="305"></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 440, Column 53: start tag was here
    …p-418-elegance-ii-bedroom-group.aspx"><img src="/images/promos/LOveBedrm.jpg" …
  • Error Line 447, Column 158: end tag for "img" omitted, but OMITTAG NO was specified
    …veLiv.jpg" alt="Woodhaven Mink Living Room Group" width="906" height="305"></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 447, Column 53: start tag was here
    …p-580-mink-sectional-sofa-group.aspx"><img src="/images/promos/LOveLiv.jpg" al…
  • Error Line 454, Column 171: end tag for "img" omitted, but OMITTAG NO was specified
    ….jpg" alt="Riversedge Antheron Dining Room Group" width="906" height="305"></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 454, Column 60: start tag was here
    …iversedge-antheron-dining-group.aspx"><img src="/images/promos/LOveDine.jpg" a…
  • Error Line 461, Column 136: end tag for "img" omitted, but OMITTAG NO was specified
    …images/promos/LOveTV.jpg" alt="LCD Flat Panel TV" width="906" height="305"></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 461, Column 47: start tag was here
    …ref="/p-614-55-1080p-flat-panel.aspx"><img src="/images/promos/LOveTV.jpg" alt…
  • Error Line 468, Column 174: end tag for "img" omitted, but OMITTAG NO was specified
    …shDyr.jpg" alt="Woodhaven Mink Living Room Group" width="906" height="305"></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 468, Column 66: start tag was here
    …y-washer-and-dryer-laundry-pair.aspx"><img src="/images/promos/LOveWshDyr.jpg"…
  • Error Line 566, Column 63: document type does not allow element "a" here
    …).html("<a href='/t-2000th-Store.aspx'><img style='width:100%;margin-top:0;' s…

    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 570, Column 178: end tag for "img" omitted, but OMITTAG NO was specified
    …_layout/text_guaranteed_low_price.png" alt="Guaranteed Low Price"></span></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 570, Column 72: start tag was here
    …<span style="guaranteedLowPriceInner"><img src="/skins/Skin_1/images/new_layou…
  • Error Line 571, Column 181: end tag for "img" omitted, but OMITTAG NO was specified
    …images/new_layout/text_latest_videos.png" alt="Latest Videos"></a></span></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 571, Column 92: start tag was here
    …nner"><a href="/t-aarons-videos.aspx"><img src="/skins/Skin_1/images/new_layou…
  • Error Line 572, Column 236: end tag for "img" omitted, but OMITTAG NO was specified
    …ited Time You Are Pre-approved up to $2000 in merchandise***"></a></span></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 572, Column 92: start tag was here
    …Inner"><a href="/t-2000th-Store.aspx"><img src="/skins/Skin_1/images/new_layou…
  • Error Line 573, Column 224: end tag for "img" omitted, but OMITTAG NO was specified
    …"Aaron's Lease Plus - Flexible and Easier than a Credit Card"></a></span></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 573, Column 90: start tag was here
    …woInner"><a href="/t-Lease-Plus.aspx"><img src="/skins/Skin_1/images/new_layou…
  • Error Line 574, Column 233: end tag for "img" omitted, but OMITTAG NO was specified
    …your_sleep_space.png" alt="Aaron's Renovate Your Sleep Space"></a></span></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 574, Column 109: start tag was here
    …f="/t-renovate-your-sleep-space.aspx"><img src="/skins/Skin_1/images/new_layou…
  • Error Line 580, Column 7: document type does not allow element "title" here
    <title>promos</title>

    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 645, Column 42: document type does not allow element "title" here
          <div class="tabsContentWrap"><title>tabbed promos</title>

    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 647, Column 117: end tag for "img" omitted, but OMITTAG NO was specified
    …promos/Preleased_guarantee.jpg" width="207" height="160" alt="Preleased"></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 647, Column 21: start tag was here
    <div class="imgDiv"><img src="/images/promos/Preleased_guarantee.jpg" width="20…
  • Error Line 661, Column 110: end tag for "img" omitted, but OMITTAG NO was specified
    …images/promos/ArnsSptWell_tab.jpg" width="207" height="160" alt="Sports"></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 661, Column 21: start tag was here
    <div class="imgDiv"><img src="/images/promos/ArnsSptWell_tab.jpg" width="207" h…
  • Error Line 664, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 664, Column 1: start tag was here
    <br>
  • Error Line 672, Column 121: end tag for "img" omitted, but OMITTAG NO was specified
    …romos/tab_logo-LuckyFullBody.jpg" width="93" height="115" alt="LuckyDog"></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 672, Column 24: start tag was here
    <div class="brandLogo"><img src="/images/promos/tab_logo-LuckyFullBody.jpg" wid…
  • Error Line 673, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 673, Column 1: start tag was here
    <br>
  • Error Line 678, Column 122: end tag for "img" omitted, but OMITTAG NO was specified
    …s/img_aarons-tv2.jpg" width="207" height="160" alt="Aaron's Commercials"></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 678, Column 21: start tag was here
    <div class="imgDiv"><img src="/images/promos/img_aarons-tv2.jpg" width="207" he…
  • Error Line 681, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 681, Column 1: start tag was here
    <br>
  • Error Line 686, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 686, Column 1: start tag was here
    <br>
  • Error Line 687, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 687, Column 1: start tag was here
    <br>
  • Error Line 692, Column 117: end tag for "img" omitted, but OMITTAG NO was specified
    …promos/AaronsTwitter.jpg" width="207" height="160" alt="Aaron's Twitter"></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 692, Column 21: start tag was here
    <div class="imgDiv"><img src="/images/promos/AaronsTwitter.jpg" width="207" hei…
  • Error Line 702, Column 109: there is no attribute "data-show-count"
    …witter-follow-button" data-show-count="false" data-size="large">Follow @Aarons…

    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 702, Column 127: there is no attribute "data-size"
    …follow-button" data-show-count="false" data-size="large">Follow @Aarons_Inc</a>

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

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

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

  • Error Line 703, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

    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 705, Column 28: end tag for "br" omitted, but OMITTAG NO was specified
    <div class="brandLogo"><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 705, Column 24: start tag was here
    <div class="brandLogo"><br>
  • Error Line 714, Column 165: end tag for "img" omitted, but OMITTAG NO was specified
    …n_1/images/img_circular.png" width="208" height="198" alt="Circular"></a></div>

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

  • Info Line 714, Column 73: start tag was here
    …arons.shoplocal.com/" target="_blank"><img src="/skins/Skin_1/images/img_circu…
  • Error Line 756, Column 134: required attribute "alt" not specified
    …t;"><img src="skins/Skin_1/images/new_layout/button_get_started_now.png" /></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 757, Column 152: required attribute "alt" not specified
    …img src="skins/Skin_1/images/new_layout/button_have_a_store_call_me.png" /></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>.

  • Warning Line 871, Column 219: character "&" is the first character of a delimiter but occurred as data
    … title="Aaron's, Inc., Furniture Rent & Lease, Atlanta, GA" style="display: bl…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 871, Column 529: character "&" is the first character of a delimiter but occurred as data
    …7" alt="Aaron's, Inc., Furniture Rent & Lease, Atlanta, GA" /></a><script type…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 902, Column 45: character "&" is the first character of a delimiter but occurred as data
    …              if (intent_event.target && intent_event.target.nodeName == 'IFRA…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 902, Column 46: character "&" is the first character of a delimiter but occurred as data
    …             if (intent_event.target && intent_event.target.nodeName == 'IFRAM…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 919, Column 45: character "&" is the first character of a delimiter but occurred as data
                    var regex = new RegExp('[\\?&#]' + paramName + '=([^&#]*)');

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 919, Column 69: character "&" is the first character of a delimiter but occurred as data
                    var regex = new RegExp('[\\?&#]' + paramName + '=([^&#]*)');

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 940, Column 128: cannot generate system identifier for general entity "name"
    …' : 'http://') + 'pixel.fetchback.com/serve/fb/pdj?cat=&name=landing&sid=3998';

    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 940, Column 128: general entity "name" not defined and no default entity
    …' : 'http://') + 'pixel.fetchback.com/serve/fb/pdj?cat=&name=landing&sid=3998';

    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 940, Column 132: reference not terminated by REFC delimiter
    …' : 'http://') + 'pixel.fetchback.com/serve/fb/pdj?cat=&name=landing&sid=3998';

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

  • Error Line 940, Column 132: reference to entity "name" for which no system identifier could be generated
    …' : 'http://') + 'pixel.fetchback.com/serve/fb/pdj?cat=&name=landing&sid=3998';

    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 940, Column 127: entity was defined here
    …' : 'http://') + 'pixel.fetchback.com/serve/fb/pdj?cat=&name=landing&sid=3998';
  • Warning Line 940, Column 141: cannot generate system identifier for general entity "sid"
    …' : 'http://') + 'pixel.fetchback.com/serve/fb/pdj?cat=&name=landing&sid=3998';

    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 940, Column 141: general entity "sid" not defined and no default entity
    …' : 'http://') + 'pixel.fetchback.com/serve/fb/pdj?cat=&name=landing&sid=3998';

    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 940, Column 144: reference not terminated by REFC delimiter
    …' : 'http://') + 'pixel.fetchback.com/serve/fb/pdj?cat=&name=landing&sid=3998';

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

  • Error Line 940, Column 144: reference to entity "sid" for which no system identifier could be generated
    …' : 'http://') + 'pixel.fetchback.com/serve/fb/pdj?cat=&name=landing&sid=3998';

    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 940, Column 140: entity was defined here
    …' : 'http://') + 'pixel.fetchback.com/serve/fb/pdj?cat=&name=landing&sid=3998';

Visitor Analysis

Daily Visitor
  • 4.200 visits
Daily Visitor