zynga.com

Best place to play free online games with friends. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 11-05-2013 09:02:57  (update).

Overview Info

  • Domain Name
    zynga.com
  • Favicon
  • Alexa Rank
    #922
  • Google Page Rank
    PR 6
  • Ip Address
    184.75.160.24
  • Page Size
    23.5 KB
  • Images
    0 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    Zynga | Play free online games with friends
  • Meta Keyword
  • Meta Description
    Best place to play free online games with friends.

Technical Analysis



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

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

HTML Analysis

  • server: nginx
  • date: Sat, 11 May 2013 09:02:52 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Matt Serlin
DNStination Inc.
303 Second Street Suite 800 North
San Francisco CA 94107
US
email +1.4155319335 Fax: +1.4155319336

Domain Name: zynga.com

Registrar Name: Markmonitor.com
Registrar Whois: whois.markmonitor.com
Registrar Homepage: http://www.markmonitor.com

Administrative Contact:
Matt Serlin
DNStination Inc.
303 Second Street Suite 800 North
San Francisco CA 94107
US
email +1.4155319335 Fax: +1.4155319336
Technical Contact, Zone Contact:
Matt Serlin
DNStination Inc.
303 Second Street Suite 800 North
San Francisco CA 94107
US
email +1.4155319335 Fax: +1.4155319336

Created on..............: 2007-11-02.
Expires on..............: 2016-11-02.
Record last updated on..: 2012-10-25.

Domain servers in listed order:

pdns6.ultradns.co.uk
pdns4.ultradns.org
pdns2.ultradns.net
pdns1.ultradns.net
pdns3.ultradns.org
pdns5.ultradns.info

DNS Analysis


DNS servers
pdns3.ultradns.org [199.7.68.1]
pdns4.ultradns.org [199.7.69.1]
pdns1.ultradns.net [204.74.108.1]
pdns2.ultradns.net [204.74.109.1]
pdns5.ultradns.info
pdns6.ultradns.co.uk [204.74.115.1]


DNS Records

Answer records
zynga.com NS  pdns1.ultradns.net 43200s
zynga.com NS  pdns2.ultradns.net 43200s
zynga.com NS  pdns3.ultradns.org 43200s
zynga.com NS  pdns4.ultradns.org 43200s
zynga.com SOA
server: pdns1.ultradns.net
email: netops@zynga.com
serial: 2013041706
refresh: 1800
retry: 300
expire: 604800
minimum ttl: 300
300s
zynga.com MX
preference: 10
exchange: C7-IP01.zynga.com
300s
zynga.com MX
preference: 10
exchange: C7-IP02.zynga.com
300s
zynga.com TXT v=spf1 a mx ptr include:service-now.com include:_spf.jobvite.com a:billingmx.zynga.com ip4:72.5.237.0/25 ip4:207.5.74.42/24 ip4:74.201.93.0/24 ip4:74.217.68.155 ip4:74.217.69.171 ip4:74.217.69.27 ip4:69.25.59.149 ip4:216.136.162.122/29 ~all 300s
zynga.com A 184.75.160.24 120s

Authority records

Additional records
C7-IP01.zynga.com A 72.5.237.23 10800s

IP 184.75.160.24 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 33 Errors
  • 14 Warnings
Ratio Text/Html
  • 0.38494194031714324
Message Error
  • Error Line 3, Column 17: there is no attribute "prefix"
       <head prefix="og: http://ogp.me/ns# playzynga:http://ogp.me/ns/apps/playzyng…

    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 4, Column 17: there is no attribute "charset"
    		<meta charset="utf-8" />

    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 4, Column 26: required attribute "content" not specified
    		<meta charset="utf-8" />

    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 5, Column 56: required attribute "type" not specified
    					<script src="//cdn.optimizely.com/js/145818352.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>.

  • Error Line 18, Column 104: end tag for "link" omitted, but OMITTAG NO was specified
    …ogleapis.com/css?family=Changa+One:400italic' rel='stylesheet' type='text/css'>

    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 18, Column 3: start tag was here
    		<link href='//fonts.googleapis.com/css?family=Changa+One:400italic' rel='styl…
  • Error Line 55, Column 34: there is no attribute "track"
    		<div id="logo-container" track="zhdr2">

    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 57, Column 67: cannot generate system identifier for general entity "aff"
    …ttps://zynga.com?src=bookmark_browser&aff=header_logo" alt="Zynga" onclick="re…

    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 57, Column 67: general entity "aff" not defined and no default entity
    …ttps://zynga.com?src=bookmark_browser&aff=header_logo" alt="Zynga" onclick="re…

    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 57, Column 70: reference not terminated by REFC delimiter
    …s://zynga.com?src=bookmark_browser&aff=header_logo" alt="Zynga" onclick="retur…

    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 57, Column 70: reference to external entity in attribute value
    …s://zynga.com?src=bookmark_browser&aff=header_logo" alt="Zynga" onclick="retur…

    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 57, Column 70: reference to entity "aff" for which no system identifier could be generated
    …s://zynga.com?src=bookmark_browser&aff=header_logo" alt="Zynga" onclick="retur…

    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 57, Column 66: entity was defined here
    …https://zynga.com?src=bookmark_browser&aff=header_logo" alt="Zynga" onclick="r…
  • Error Line 57, Column 88: there is no attribute "alt"
    …a.com?src=bookmark_browser&aff=header_logo" alt="Zynga" onclick="return false">

    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 83, Column 3710: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    …ker</a><li class="zy-game-index-group"><div class="zy-game-index-letter-headin…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 83, Column 4077: end tag for "li" omitted, but OMITTAG NO was specified
    …n-games">Simulation Games</a></li></div>							<div class="zy-seo-description">

    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 83, Column 3460: start tag was here
    …</ul><ul class="zy-game-index-column"><li class="zy-game-index-group"><div cla…
  • Error Line 83, Column 4077: end tag for "ul" omitted, but OMITTAG NO was specified
    …n-games">Simulation Games</a></li></div>							<div class="zy-seo-description">

    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 83, Column 3427: start tag was here
    …d Sale: Hidden Treasures</a></li></ul><ul class="zy-game-index-column"><li cla…
  • Error Line 95, Column 49: there is no attribute "target"
    		<li><a href="http://company.zynga.com" target="_blank">Company</a></li>

    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 129, Column 53: required attribute "type" not specified
    			<script src="//connect.facebook.net/en_US/all.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 135, Column 16253: cannot generate system identifier for general entity "gameId"
    …om\/CP_Suggestions_WebFull?feedback=0&gameId=1031&custlayoutid=1&layout=webFul…

    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 135, Column 16253: general entity "gameId" not defined and no default entity
    …om\/CP_Suggestions_WebFull?feedback=0&gameId=1031&custlayoutid=1&layout=webFul…

    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 135, Column 16259: reference not terminated by REFC delimiter
    …_Suggestions_WebFull?feedback=0&gameId=1031&custlayoutid=1&layout=webFull&layo…

    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 135, Column 16259: reference to entity "gameId" for which no system identifier could be generated
    …_Suggestions_WebFull?feedback=0&gameId=1031&custlayoutid=1&layout=webFull&layo…

    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 135, Column 16252: entity was defined here
    …com\/CP_Suggestions_WebFull?feedback=0&gameId=1031&custlayoutid=1&layout=webFu…
  • Warning Line 135, Column 16265: cannot generate system identifier for general entity "custlayoutid"
    …stions_WebFull?feedback=0&gameId=1031&custlayoutid=1&layout=webFull&layouttmpl…

    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 135, Column 16265: general entity "custlayoutid" not defined and no default entity
    …stions_WebFull?feedback=0&gameId=1031&custlayoutid=1&layout=webFull&layouttmpl…

    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 135, Column 16277: reference not terminated by REFC delimiter
    …ll?feedback=0&gameId=1031&custlayoutid=1&layout=webFull&layouttmpl=Tmpl_WebFul…

    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 135, Column 16277: reference to entity "custlayoutid" for which no system identifier could be generated
    …ll?feedback=0&gameId=1031&custlayoutid=1&layout=webFull&layouttmpl=Tmpl_WebFul…

    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 135, Column 16264: entity was defined here
    …estions_WebFull?feedback=0&gameId=1031&custlayoutid=1&layout=webFull&layouttmp…
  • Warning Line 135, Column 16280: cannot generate system identifier for general entity "layout"
    …feedback=0&gameId=1031&custlayoutid=1&layout=webFull&layouttmpl=Tmpl_WebFull_1…

    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 135, Column 16280: general entity "layout" not defined and no default entity
    …feedback=0&gameId=1031&custlayoutid=1&layout=webFull&layouttmpl=Tmpl_WebFull_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.

  • Warning Line 135, Column 16286: reference not terminated by REFC delimiter
    …ck=0&gameId=1031&custlayoutid=1&layout=webFull&layouttmpl=Tmpl_WebFull_1&loc="…

    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 135, Column 16286: reference to entity "layout" for which no system identifier could be generated
    …ck=0&gameId=1031&custlayoutid=1&layout=webFull&layouttmpl=Tmpl_WebFull_1&loc="…

    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 135, Column 16279: entity was defined here
    …?feedback=0&gameId=1031&custlayoutid=1&layout=webFull&layouttmpl=Tmpl_WebFull_…
  • Warning Line 135, Column 16295: cannot generate system identifier for general entity "layouttmpl"
    …Id=1031&custlayoutid=1&layout=webFull&layouttmpl=Tmpl_WebFull_1&loc=","zdc_ads…

    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 135, Column 16295: general entity "layouttmpl" not defined and no default entity
    …Id=1031&custlayoutid=1&layout=webFull&layouttmpl=Tmpl_WebFull_1&loc=","zdc_ads…

    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 135, Column 16305: reference not terminated by REFC delimiter
    …stlayoutid=1&layout=webFull&layouttmpl=Tmpl_WebFull_1&loc=","zdc_ads_bac_uri":…

    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 135, Column 16305: reference to entity "layouttmpl" for which no system identifier could be generated
    …stlayoutid=1&layout=webFull&layouttmpl=Tmpl_WebFull_1&loc=","zdc_ads_bac_uri":…

    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 135, Column 16294: entity was defined here
    …eId=1031&custlayoutid=1&layout=webFull&layouttmpl=Tmpl_WebFull_1&loc=","zdc_ad…
  • Warning Line 135, Column 16321: cannot generate system identifier for general entity "loc"
    …out=webFull&layouttmpl=Tmpl_WebFull_1&loc=","zdc_ads_bac_uri":"\/\/zynga2-a.ak…

    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 135, Column 16321: general entity "loc" not defined and no default entity
    …out=webFull&layouttmpl=Tmpl_WebFull_1&loc=","zdc_ads_bac_uri":"\/\/zynga2-a.ak…

    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 135, Column 16324: reference not terminated by REFC delimiter
    …=webFull&layouttmpl=Tmpl_WebFull_1&loc=","zdc_ads_bac_uri":"\/\/zynga2-a.akama…

    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 135, Column 16324: reference to entity "loc" for which no system identifier could be generated
    …=webFull&layouttmpl=Tmpl_WebFull_1&loc=","zdc_ads_bac_uri":"\/\/zynga2-a.akama…

    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 135, Column 16320: entity was defined here
    …yout=webFull&layouttmpl=Tmpl_WebFull_1&loc=","zdc_ads_bac_uri":"\/\/zynga2-a.a…
  • Error Line 158, Column 42: document type does not allow element "div" here
    								'<div class="zy-banned-container"></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).

Visitor Analysis

Daily Visitor
  • 140.000 visits
Daily Visitor

In Page Analysis