Große Auswahl an Markenprodukten wie Haushaltsgeräte, LCD und Plasma TV, Digitalkameras, Notebooks, Camcorder und vieles mehr zu günstigen Preisen! ...

redcoon.at
  • Domain Name
    redcoon.at
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #61682
  • Page Size
    94.6 KB
  • Ip Address
    91.202.50.73
  • Heading
    H1: 1, H2: 5, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    28 GIF, 12 JPG, 168 PNG

Website Meta Analysis

  • Title
    Elektronik und Unterhaltungselektronik günstig | redcoon Österreich
  • Meta Keyword
  • Meta Description
    Große Auswahl an Markenprodukten wie Haushaltsgeräte, LCD und Plasma TV, Digitalkameras, Notebooks, Camcorder und vieles mehr zu günstigen Preisen!

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    91.202.50.73
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from redcoon.at.

HTML Analysis

  • server: nginx
  • content-type: text/html; charset=UTF-8
  • vary: Accept-Encoding
  • p3p: CP="OUR DSP OTP OUR BUS PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA HEA PRE LOC GOV OTC"
  • pragma: public
  • content-encoding: gzip
  • content-length: 18514
  • cache-control: public, max-age=1037
  • expires: Mon, 25 Feb 2013 14:18:20 GMT
  • date: Mon, 25 Feb 2013 14:01:03 GMT
  • connection: keep-alive
  • age: 16
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
No data whois for redcoon.at

DNS Analysis


DNS servers
sparks.twooit.com
trinity.twooit.com
tank.twooit.com


DNS Records

Answer records
redcoon.at SOA
server: tank.twooit.com
email: hostmaster@twooit.com
serial: 2012112003
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
3600s
redcoon.at NS  tank.twooit.com 3600s
redcoon.at A 91.202.50.73 300s
redcoon.at MX
preference: 10
exchange: mail01.datacenter-coburg.de
3600s
redcoon.at NS  trinity.twooit.com 3600s
redcoon.at NS  sparks.twooit.com 3600s

Authority records

Additional records
sparks.twooit.com A 95.129.49.9 3600s
tank.twooit.com A 95.129.51.50 3600s
trinity.twooit.com A 178.63.94.19 3600s

IP 91.202.50.73 Analysis

  • Country Code
    DE
  • Country Code3
    DEU
  • Country Name
    Germany
  • City
    EU
  • Continent Code
    51° North
  • Latitude
    9.
  • Longitude
  • No whois ip data for 91.202.50.73

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 27 Errors
  • 26 Warnings
Ratio Text/Html
  • 0.7273233912998607
Message Error
  • Error Line 14, Column 36: there is no attribute "sizes"
    <link rel="apple-touch-icon" sizes="114x114" href="http://www.redcoon.at/res/Im…

    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 122, Column 151: character "&" is the first character of a delimiter but occurred as data
    …Slide('contactwidget' , 'accountwidget');return false;">KONTAKT & LIVE-CHAT</a>

    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 126, Column 158: character "&" is the first character of a delimiter but occurred as data
    …lockSlide('contactwidget' , 'accountwidget');return false;">KONTAKT & LIVE-CHAT

    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.
  • Error Line 183, Column 52: there is no attribute "autocomplete"
    <form action="https://www.redcoon.at" autocomplete="off" method="post">

    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 514, Column 211: end tag for "img" omitted, but OMITTAG NO was specified
    …t="Jetzt zum redcoon Newsletter anmelden!" width="190" height="190"></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 514, Column 80: start tag was here
    …<a href="https://www.redcoon.at/news"><img src="/res/Image/left_column/newslet…
  • Error Line 541, Column 355: there is no attribute "allowTransparency"
    … overflow:hidden; width:125px; height:21px;" 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.

  • Error Line 543, Column 34: there is no attribute "data-size"
    <div class="g-plusone" data-size="medium"></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 551, Column 76: there is no attribute "data-lang"
    …ttps://twitter.com/share" class="twitter-share-button" data-lang="de">Tweet</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 552, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){ var js,fjs=d.getElementsByTagName(s)[0];if(!d.getEle…

    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 905, Column 58: character "&" is the first character of a delimiter but occurred as data
    … title="Monochrom Laserdrucker Duplex & LAN">Monochrom Laserdrucker Duplex & L…

    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 905, Column 95: character "&" is the first character of a delimiter but occurred as data
    …e="Monochrom Laserdrucker Duplex & LAN">Monochrom Laserdrucker Duplex & LAN</p>

    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.
  • Error Line 1001, Column 48: "Core" is not a member of a group specified for any attribute
    …"slh sllg" title="Notebook 17,3" Core i5-3210M 750GB 4GB">Notebook 17,3" Core …
  • Error Line 1001, Column 57: "i5-3210M" is not a member of a group specified for any attribute
    …" title="Notebook 17,3" Core i5-3210M 750GB 4GB">Notebook 17,3" Core i5-3210M …
  • Error Line 1001, Column 57: "750GB" is not a member of a group specified for any attribute
    …" title="Notebook 17,3" Core i5-3210M 750GB 4GB">Notebook 17,3" Core i5-3210M …
  • Error Line 1001, Column 63: "4GB" is not a member of a group specified for any attribute
    …e="Notebook 17,3" Core i5-3210M 750GB 4GB">Notebook 17,3" Core i5-3210M 750GB …
  • Error Line 1001, Column 66: an attribute specification must start with a name or name token
    …Notebook 17,3" Core i5-3210M 750GB 4GB">Notebook 17,3" Core i5-3210M 750GB 4GB…

    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).

  • Warning Line 1172, Column 49: character "&" is the first character of a delimiter but occurred as data
    … match = location.href.match(new RegExp("[?&]" + parameter + "[=][^&]*", "i"));

    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 1172, Column 73: character "&" is the first character of a delimiter but occurred as data
    … match = location.href.match(new RegExp("[?&]" + parameter + "[=][^&]*", "i"));

    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 1188, Column 39: character "&" is the first character of a delimiter but occurred as data
    		if (document.referrer.split('/')[2] && !IsSameWebsite() && !ExistsCPID())

    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 1188, Column 40: character "&" is the first character of a delimiter but occurred as data
    		if (document.referrer.split('/')[2] && !IsSameWebsite() && !ExistsCPID())

    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 1188, Column 59: character "&" is the first character of a delimiter but occurred as data
    		if (document.referrer.split('/')[2] && !IsSameWebsite() && !ExistsCPID())

    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 1188, Column 60: character "&" is the first character of a delimiter but occurred as data
    		if (document.referrer.split('/')[2] && !IsSameWebsite() && !ExistsCPID())

    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 1192, Column 17: character "&" is the first character of a delimiter but occurred as data
    				if (success && refData != "0")

    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 1192, Column 18: character "&" is the first character of a delimiter but occurred as data
    				if (success && refData != "0")

    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 1196, Column 87: cannot generate system identifier for general entity "pl_id"
    …oon.clickfire.de/track/add_cl?pg_id=2&pl_id=" + pl_id + "&ref_track=1" + "&ref…

    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 1196, Column 87: general entity "pl_id" not defined and no default entity
    …oon.clickfire.de/track/add_cl?pg_id=2&pl_id=" + pl_id + "&ref_track=1" + "&ref…

    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 1196, Column 92: reference not terminated by REFC delimiter
    …lickfire.de/track/add_cl?pg_id=2&pl_id=" + pl_id + "&ref_track=1" + "&ref_orig…

    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 1196, Column 92: reference to entity "pl_id" for which no system identifier could be generated
    …lickfire.de/track/add_cl?pg_id=2&pl_id=" + pl_id + "&ref_track=1" + "&ref_orig…

    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 1196, Column 86: entity was defined here
    …coon.clickfire.de/track/add_cl?pg_id=2&pl_id=" + pl_id + "&ref_track=1" + "&re…
  • Warning Line 1196, Column 107: cannot generate system identifier for general entity "ref_track"
    …ck/add_cl?pg_id=2&pl_id=" + pl_id + "&ref_track=1" + "&ref_orig_url=" + docume…

    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 1196, Column 107: general entity "ref_track" not defined and no default entity
    …ck/add_cl?pg_id=2&pl_id=" + pl_id + "&ref_track=1" + "&ref_orig_url=" + docume…

    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 1196, Column 116: reference not terminated by REFC delimiter
    …?pg_id=2&pl_id=" + pl_id + "&ref_track=1" + "&ref_orig_url=" + document.referr…

    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 1196, Column 116: reference to entity "ref_track" for which no system identifier could be generated
    …?pg_id=2&pl_id=" + pl_id + "&ref_track=1" + "&ref_orig_url=" + document.referr…

    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 1196, Column 106: entity was defined here
    …ack/add_cl?pg_id=2&pl_id=" + pl_id + "&ref_track=1" + "&ref_orig_url=" + docum…
  • Warning Line 1196, Column 124: cannot generate system identifier for general entity "ref_orig_url"
    …g_id=2&pl_id=" + pl_id + "&ref_track=1" + "&ref_orig_url=" + document.referrer;

    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 1196, Column 124: general entity "ref_orig_url" not defined and no default entity
    …g_id=2&pl_id=" + pl_id + "&ref_track=1" + "&ref_orig_url=" + document.referrer;

    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 1196, Column 136: reference not terminated by REFC delimiter
    …g_id=2&pl_id=" + pl_id + "&ref_track=1" + "&ref_orig_url=" + document.referrer;

    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 1196, Column 136: reference to entity "ref_orig_url" for which no system identifier could be generated
    …g_id=2&pl_id=" + pl_id + "&ref_track=1" + "&ref_orig_url=" + document.referrer;

    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 1196, Column 123: entity was defined here
    …g_id=2&pl_id=" + pl_id + "&ref_track=1" + "&ref_orig_url=" + document.referrer;
  • Error Line 1209, Column 8: required attribute "type" not specified
    <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 1241, Column 14: cannot generate system identifier for general entity "xtcr"
    							  + "&xtcr=" + posCounter;

    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 1241, Column 14: general entity "xtcr" not defined and no default entity
    							  + "&xtcr=" + posCounter;

    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 1241, Column 18: reference not terminated by REFC delimiter
    							  + "&xtcr=" + posCounter;

    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 1241, Column 18: reference to entity "xtcr" for which no system identifier could be generated
    							  + "&xtcr=" + posCounter;

    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 1241, Column 13: entity was defined here
    							  + "&xtcr=" + posCounter;
  • Warning Line 1250, Column 48: cannot generate system identifier for general entity "mc"
    		if (window.xtparam!=null){ window.xtparam+="&mc="+xt_mtcl+"&np="+xt_npg; }

    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 1250, Column 48: general entity "mc" not defined and no default entity
    		if (window.xtparam!=null){ window.xtparam+="&mc="+xt_mtcl+"&np="+xt_npg; }

    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 1250, Column 50: reference not terminated by REFC delimiter
    		if (window.xtparam!=null){ window.xtparam+="&mc="+xt_mtcl+"&np="+xt_npg; }

    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 1250, Column 50: reference to entity "mc" for which no system identifier could be generated
    		if (window.xtparam!=null){ window.xtparam+="&mc="+xt_mtcl+"&np="+xt_npg; }

    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 1250, Column 47: entity was defined here
    		if (window.xtparam!=null){ window.xtparam+="&mc="+xt_mtcl+"&np="+xt_npg; }
  • Warning Line 1250, Column 63: cannot generate system identifier for general entity "np"
    		if (window.xtparam!=null){ window.xtparam+="&mc="+xt_mtcl+"&np="+xt_npg; }

    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 1250, Column 63: general entity "np" not defined and no default entity
    		if (window.xtparam!=null){ window.xtparam+="&mc="+xt_mtcl+"&np="+xt_npg; }

    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 1250, Column 65: reference not terminated by REFC delimiter
    		if (window.xtparam!=null){ window.xtparam+="&mc="+xt_mtcl+"&np="+xt_npg; }

    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 1250, Column 65: reference to entity "np" for which no system identifier could be generated
    		if (window.xtparam!=null){ window.xtparam+="&mc="+xt_mtcl+"&np="+xt_npg; }

    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 1250, Column 62: entity was defined here
    		if (window.xtparam!=null){ window.xtparam+="&mc="+xt_mtcl+"&np="+xt_npg; }
  • Warning Line 1251, Column 29: reference not terminated by REFC delimiter
    		else{ window.xtparam ="&mc="+xt_mtcl+"&np="+xt_npg; }

    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 1251, Column 29: reference to entity "mc" for which no system identifier could be generated
    		else{ window.xtparam ="&mc="+xt_mtcl+"&np="+xt_npg; }

    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 1250, Column 47: entity was defined here
    		if (window.xtparam!=null){ window.xtparam+="&mc="+xt_mtcl+"&np="+xt_npg; }
  • Warning Line 1251, Column 44: reference not terminated by REFC delimiter
    		else{ window.xtparam ="&mc="+xt_mtcl+"&np="+xt_npg; }

    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 1251, Column 44: reference to entity "np" for which no system identifier could be generated
    		else{ window.xtparam ="&mc="+xt_mtcl+"&np="+xt_npg; }

    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 1250, Column 62: entity was defined here
    		if (window.xtparam!=null){ window.xtparam+="&mc="+xt_mtcl+"&np="+xt_npg; }

Visitor Analysis

Daily Visitor
  • 2.333 visits
Daily Visitor