bossip.com

Bossip is the premier destination for African-American and Black Celebrity Gossip and Entertainment News, Covering African-American and Black Celebrities, News, and Black Hollywood Rumors. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 13-09-2013 04:07:29  (update).

Overview Info

  • Domain Name
    bossip.com
  • Favicon
  • Alexa Rank
    #3850
  • Google Page Rank
    PR 6
  • Ip Address
    76.74.255.117
  • Page Size
    84.6 KB
  • Images
    1 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 7 21 2 0 0

Website Meta Analysis



  • Meta Keyword
    bossip, celebrity gossip, celebrity news, black celebrity gossip, black celebrity news, kim kardashian, kat stacks exposed, nicki minaj, natalie nunn, amber rose, lisa raye, lil wayne
  • Meta Description
    Bossip is the premier destination for African-American and Black Celebrity Gossip and Entertainment News, Covering African-American and Black Celebrities, News, and Black Hollywood Rumors.

Technical Analysis



  • Webserver
    nginx
  • Ip Address
    76.74.255.117
  • Domain Age
    7 Years, 5 Months, 24 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Fri, 13 Sep 2013 16:07:26 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • last-modified: Fri, 13 Sep 2013 16:01:15 GMT
  • cache-control: max-age=229, must-revalidate
  • x-nananana: Batcache
  • x-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.
  • x-pingback: http://bossip.com/xmlrpc.php
  • link: ; rel=shortlink
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States

Domain Name: BOSSIP.COM
Created on: 30-Mar-06
Expires on: 30-Mar-13
Last Updated on: 30-Nov-08

Administrative Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Technical Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

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

DNS Analysis


DNS servers
ns1.wordpress.com [72.233.69.14]
ns2.wordpress.com [69.174.248.148]

DNS Records

Answer records
bossip.com SOA
server: ns1.wordpress.com
email: hostmaster@wordpress.com
serial: 2005071858
refresh: 14400
retry: 7200
expire: 604800
minimum ttl: 300
86400s
bossip.com A 76.74.254.120 300s
bossip.com A 72.233.104.125 300s
bossip.com A 74.200.247.59 300s
bossip.com NS  ns1.wordpress.com 14400s
bossip.com NS  ns2.wordpress.com 14400s
bossip.com NS  ns3.wordpress.com 14400s
bossip.com TXT v=spf1 include:aspmx.googlemail.com ~all 3600s
bossip.com TXT v=spf1 mx include:cmail1.com ~all 3600s
bossip.com MX
preference: 1
exchange: ASPMX.L.GOOGLE.com
3600s
bossip.com MX
preference: 5
exchange: ALT2.ASPMX.L.GOOGLE.com
3600s
bossip.com MX
preference: 5
exchange: ALT1.ASPMX.L.GOOGLE.com
3600s
bossip.com MX
preference: 10
exchange: ASPMX2.GOOGLEMAIL.com
3600s
bossip.com MX
preference: 10
exchange: ASPMX3.GOOGLEMAIL.com
3600s
bossip.com MX
preference: 10
exchange: mail.bossip.com
3600s
bossip.com A 72.233.104.123 300s
bossip.com A 74.200.247.61 300s
bossip.com A 76.74.254.121 300s

Authority records

Additional records
mail.bossip.com CNAME ghs.GOOGLE.com 3600s

IP 76.74.255.117 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    San Antonio
  • Continent Code
    78201
  • Latitude
    210
  • Longitude
    641
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 76.74.255.117"
    #
    # Use "?" to get help.
    #

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

    ServerBeach PEER1-SERVERBEACH-08A (NET-76-74-248-0-1) 76.74.248.0 - 76.74.255.255
    Peer 1 Network Inc. PEER1-BLK-10 (NET-76-74-128-0-1) 76.74.128.0 - 76.74.255.255
    Automattic, Inc PEER1--AUTOMATTIC-SERVERBEACH-ACCOUNT--01 (NET-76-74-255-0-1) 76.74.255.0 - 76.74.255.127


    #
    # 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
  • 72 Errors
  • 40 Warnings
Ratio Text/Html
  • 0.6953757025308421
Message Error
  • Error Line 12, Column 13: there is no attribute "name"
    	<META name="y_key" content="62eb6831392680c3" />

    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 12, Column 29: there is no attribute "content"
    	<META name="y_key" content="62eb6831392680c3" />

    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 12, Column 49: element "META" undefined
    	<META name="y_key" content="62eb6831392680c3" />

    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 82, Column 9: required attribute "type" not specified
    		<style>

    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 122, Column 108: character "&" is the first character of a delimiter but occurred as data
    …uery(document).scrollTop()>=document.body.offsetHeight-500&&inProgress==false){

    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 122, Column 110: cannot generate system identifier for general entity "inProgress"
    …uery(document).scrollTop()>=document.body.offsetHeight-500&&inProgress==false){

    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 122, Column 110: general entity "inProgress" not defined and no default entity
    …uery(document).scrollTop()>=document.body.offsetHeight-500&&inProgress==false){

    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 122, Column 120: reference not terminated by REFC delimiter
    …uery(document).scrollTop()>=document.body.offsetHeight-500&&inProgress==false){

    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 122, Column 120: reference to entity "inProgress" for which no system identifier could be generated
    …uery(document).scrollTop()>=document.body.offsetHeight-500&&inProgress==false){

    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 122, Column 109: entity was defined here
    …uery(document).scrollTop()>=document.body.offsetHeight-500&&inProgress==false){
  • Error Line 124, Column 64: document type does not allow element "div" here
    …append('<div class="loading-indicator"><img src="http://s2.wp.com/wp-content/t…

    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 124, Column 155: required attribute "alt" not specified
    …sip3/images/loading.gif?m=1358877707g"><p>Loading more articles...</p></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 124, Column 156: end tag for "img" omitted, but OMITTAG NO was specified
    …sip3/images/loading.gif?m=1358877707g"><p>Loading more articles...</p></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 124, Column 65: start tag was here
    …ppend('<div class="loading-indicator"><img src="http://s2.wp.com/wp-content/th…
  • Error Line 138, Column 401: there is no attribute "property"
    …://s2.wp.com/i/favicon.ico" /><meta property="og:site_name" content="Bossip" />

    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 246, Column 431: there is no attribute "allowTransparency"
    …:relative;margin-top:4px;margin-bottom:5px;" allowTransparency="true"></iframe>

    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.

  • Warning Line 249, Column 70: cannot generate system identifier for general entity "p"
    …nstantcontact.com/d.jsp?llr=w6fyyrdab&p=oi&m=1103329236918" target="_blank" cl…

    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 249, Column 70: general entity "p" not defined and no default entity
    …nstantcontact.com/d.jsp?llr=w6fyyrdab&p=oi&m=1103329236918" target="_blank" cl…

    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 249, Column 71: reference not terminated by REFC delimiter
    …stantcontact.com/d.jsp?llr=w6fyyrdab&p=oi&m=1103329236918" target="_blank" cla…

    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 249, Column 71: reference to external entity in attribute value
    …stantcontact.com/d.jsp?llr=w6fyyrdab&p=oi&m=1103329236918" target="_blank" cla…

    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 249, Column 71: reference to entity "p" for which no system identifier could be generated
    …stantcontact.com/d.jsp?llr=w6fyyrdab&p=oi&m=1103329236918" target="_blank" cla…

    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 249, Column 69: entity was defined here
    …onstantcontact.com/d.jsp?llr=w6fyyrdab&p=oi&m=1103329236918" target="_blank" c…
  • Warning Line 249, Column 75: cannot generate system identifier for general entity "m"
    …tcontact.com/d.jsp?llr=w6fyyrdab&p=oi&m=1103329236918" target="_blank" class="…

    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 249, Column 75: general entity "m" not defined and no default entity
    …tcontact.com/d.jsp?llr=w6fyyrdab&p=oi&m=1103329236918" target="_blank" class="…

    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 249, Column 76: reference not terminated by REFC delimiter
    …contact.com/d.jsp?llr=w6fyyrdab&p=oi&m=1103329236918" target="_blank" class="n…

    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 249, Column 76: reference to external entity in attribute value
    …contact.com/d.jsp?llr=w6fyyrdab&p=oi&m=1103329236918" target="_blank" class="n…

    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 249, Column 76: reference to entity "m" for which no system identifier could be generated
    …contact.com/d.jsp?llr=w6fyyrdab&p=oi&m=1103329236918" target="_blank" class="n…

    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 249, Column 74: entity was defined here
    …ntcontact.com/d.jsp?llr=w6fyyrdab&p=oi&m=1103329236918" target="_blank" class=…
  • Error Line 263, Column 41: there is no attribute "data-vr-zone"
        	<div id="featContent" data-vr-zone="Featured Posts">

    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 264, Column 59: there is no attribute "data-vr-contentbox"
            				<div class="featureSlot-1" data-vr-contentbox="">

    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 269, Column 275: there is no attribute "rel"
    …ts-icon"><span class="dsq-postid" rel="735285 http://bossip.com/?p=735285">Vie…

    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 404, Column 37: there is no attribute "data-src"
    					<div class="OUTBRAIN" data-src="http://www.bossip.com" data-widget-id="AR_…

    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 404, Column 76: there is no attribute "data-widget-id"
    …"http://www.bossip.com" data-widget-id="AR_2" data-ob-template="bossip" ></div>

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

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

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

  • Error Line 404, Column 100: there is no attribute "data-ob-template"
    …"http://www.bossip.com" data-widget-id="AR_2" data-ob-template="bossip" ></div>

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

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

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

  • Error Line 405, Column 43: there is no attribute "async"
    …	<script type="text/javascript" async="async" src="http://widgets.outbrain.com…

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

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

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

  • Error Line 770, Column 40: character "'" is not allowed in the value of attribute "id"
    			document.write('<div id="_CI_widget_');

    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 770, Column 43: value of attribute "id" must be a single token
    			document.write('<div id="_CI_widget_');

    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 771, Column 18: character "(" is not allowed in the value of attribute "id"
    			document.write(_CI.counter+'"></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 771, Column 33: document type does not allow element "div" here
    			document.write(_CI.counter+'"></div>');

    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 1023, Column 8: required attribute "type" not specified
    <script>jQuery(document).ready(function($){ Gravatar.profile_cb = function( h, …

    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 1031, Column 10: ID "fb-root" already defined
    <div id="fb-root"></div><script type="text/javascript">(function(d){var id="fac…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 203, Column 10: ID "fb-root" first defined here
    <div id="fb-root"></div>
  • Warning Line 1053, Column 107: cannot generate system identifier for general entity "v"
    …stats.wordpress.com/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&ra…

    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 1053, Column 107: general entity "v" not defined and no default entity
    …stats.wordpress.com/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&ra…

    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 1053, Column 108: reference not terminated by REFC delimiter
    …tats.wordpress.com/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&ran…

    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 1053, Column 108: reference to entity "v" for which no system identifier could be generated
    …tats.wordpress.com/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&ran…

    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 1053, Column 106: entity was defined here
    …/stats.wordpress.com/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&r…
  • Warning Line 1053, Column 117: cannot generate system identifier for general entity "tz"
    …press.com/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.…

    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 1053, Column 117: general entity "tz" not defined and no default entity
    …press.com/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.…

    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 1053, Column 119: reference not terminated by REFC delimiter
    …ess.com/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.ra…

    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 1053, Column 119: reference to entity "tz" for which no system identifier could be generated
    …ess.com/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.ra…

    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 1053, Column 116: entity was defined here
    …dpress.com/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math…
  • Warning Line 1053, Column 123: cannot generate system identifier for general entity "user_id"
    …com/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.random…

    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 1053, Column 123: general entity "user_id" not defined and no default entity
    …com/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.random…

    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 1053, Column 130: reference not terminated by REFC delimiter
    …/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.random();}

    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 1053, Column 130: reference to entity "user_id" for which no system identifier could be generated
    …/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.random();}

    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 1053, Column 122: entity was defined here
    ….com/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.rando…
  • Warning Line 1053, Column 133: cannot generate system identifier for general entity "subd"
    …/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.random();}

    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 1053, Column 133: general entity "subd" not defined and no default entity
    …/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.random();}

    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 1053, Column 137: reference not terminated by REFC delimiter
    …/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.random();}

    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 1053, Column 137: reference to entity "subd" for which no system identifier could be generated
    …/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.random();}

    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 1053, Column 132: entity was defined here
    …/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.random();}
  • Warning Line 1053, Column 145: cannot generate system identifier for general entity "rand"
    …/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.random();}

    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 1053, Column 145: general entity "rand" not defined and no default entity
    …/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.random();}

    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 1053, Column 149: reference not terminated by REFC delimiter
    …/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.random();}

    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 1053, Column 149: reference to entity "rand" for which no system identifier could be generated
    …/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.random();}

    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 1053, Column 144: entity was defined here
    …/g.gif?blog=568005&v=wpcomvt&tz=-5&user_id=0&subd=bossip&rand="+Math.random();}
  • Error Line 1071, Column 18: there is no attribute "LANGUAGE"
    <script LANGUAGE="JavaScript">var OBCTm='1297970351836'; </script>

    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 1071, Column 30: required attribute "type" not specified
    <script LANGUAGE="JavaScript">var OBCTm='1297970351836'; </script>

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

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

  • Error Line 1072, Column 73: required attribute "type" not specified
    …ript LANGUAGE="JavaScript" src="http://widgets.outbrain.com/claim.js"></script>

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

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

  • Warning Line 1076, Column 87: cannot generate system identifier for general entity "pubId"
    …l.adsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></scr…

    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 1076, Column 87: general entity "pubId" not defined and no default entity
    …l.adsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></scr…

    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 1076, Column 92: reference not terminated by REFC delimiter
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>

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

  • Warning Line 1076, Column 92: reference to external entity in attribute value
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>

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

  • Error Line 1076, Column 92: reference to entity "pubId" for which no system identifier could be generated
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>

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

  • Info Line 1076, Column 86: entity was defined here
    …el.adsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></sc…
  • Warning Line 1076, Column 100: cannot generate system identifier for general entity "advId"
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1076, Column 100: general entity "advId" not defined and no default entity
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>

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

  • Warning Line 1076, Column 105: reference not terminated by REFC delimiter
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>

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

  • Warning Line 1076, Column 105: reference to external entity in attribute value
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>

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

  • Error Line 1076, Column 105: reference to entity "advId" for which no system identifier could be generated
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>

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

  • Info Line 1076, Column 99: entity was defined here
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>
  • Warning Line 1076, Column 107: cannot generate system identifier for general entity "campId"
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1076, Column 107: general entity "campId" not defined and no default entity
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>

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

  • Warning Line 1076, Column 113: reference not terminated by REFC delimiter
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>

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

  • Warning Line 1076, Column 113: reference to external entity in attribute value
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>

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

  • Error Line 1076, Column 113: reference to entity "campId" for which no system identifier could be generated
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>

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

  • Info Line 1076, Column 106: entity was defined here
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>
  • Error Line 1077, Column 18: an attribute specification must start with a name or name token
    <noscript><imgsrc=" http://pixel.adsafeprotected.com?anId=5005&pubId=Bossip&adv…

    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 1077, Column 18: element "imgsrc" undefined
    <noscript><imgsrc=" http://pixel.adsafeprotected.com?anId=5005&pubId=Bossip&adv…

    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).
  • Warning Line 1077, Column 69: reference not terminated by REFC delimiter
    …el.adsafeprotected.com?anId=5005&pubId=Bossip&advId=&campId=Bossip"></noscript…

    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 1077, Column 69: reference to entity "pubId" for which no system identifier could be generated
    …el.adsafeprotected.com?anId=5005&pubId=Bossip&advId=&campId=Bossip"></noscript…

    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 1076, Column 86: entity was defined here
    …el.adsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></sc…
  • Warning Line 1077, Column 82: reference not terminated by REFC delimiter
    …el.adsafeprotected.com?anId=5005&pubId=Bossip&advId=&campId=Bossip"></noscript>

    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 1077, Column 82: reference to entity "advId" for which no system identifier could be generated
    …el.adsafeprotected.com?anId=5005&pubId=Bossip&advId=&campId=Bossip"></noscript>

    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 1076, Column 99: entity was defined here
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>
  • Warning Line 1077, Column 90: reference not terminated by REFC delimiter
    …el.adsafeprotected.com?anId=5005&pubId=Bossip&advId=&campId=Bossip"></noscript>

    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 1077, Column 90: reference to entity "campId" for which no system identifier could be generated
    …el.adsafeprotected.com?anId=5005&pubId=Bossip&advId=&campId=Bossip"></noscript>

    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 1076, Column 106: entity was defined here
    …dsafeprotected.com/jspix?anId=5005&pubId=Bossip&advId=&campId=Bossip"></script>
  • Error Line 1077, Column 109: end tag for "imgsrc" omitted, but OMITTAG NO was specified
    …el.adsafeprotected.com?anId=5005&pubId=Bossip&advId=&campId=Bossip"></noscript>

    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 1077, Column 11: start tag was here
    <noscript><imgsrc=" http://pixel.adsafeprotected.com?anId=5005&pubId=Bossip&adv…

Visitor Analysis

Daily Visitor
  • 35.000 visits

In Page Analysis