Παίξε στην sportingbet.gr με το καλύτερο live στοιχημα, δωρεάν παιχνίδια, καζίνο, παιχνίδια πόκερ και κέρδισε τις μεγαλύτερες προσφορές. Best online poker, and bet bonus. ...

sportingbet.gr
  • Domain Name
    sportingbet.gr
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #59933
  • Page Size
    26.8 KB
  • Ip Address
    195.178.6.222
  • Heading
    H1: 2, H2: 3, H3: 4, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 16 JPG, 1 PNG

Website Meta Analysis

  • Title
    Στοίχημα, καζίνο, παιχνίδια, on line poker | Live stoixima, kazino | Sportingbet.gr
  • Meta Keyword
    Sportingbet.gr, sportsbook, bet, sport, στοίχημα, αποδόσεις, casino, ζωντανό καζίνο, live dealer, παιχνίδια, games, πόκερ, bonus
  • Meta Description
    Παίξε στην sportingbet.gr με το καλύτερο live στοιχημα, δωρεάν παιχνίδια, καζίνο, παιχνίδια πόκερ και κέρδισε τις μεγαλύτερες προσφορές. Best online poker, and bet bonus.

Technical Analysis

  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    195.178.6.222
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from sportingbet.gr.

HTML Analysis

  • cache-control: private
  • date: Tue, 13 Aug 2013 00:55:08 GMT
  • content-type: text/html; charset=utf-8
  • server: Microsoft-IIS/6.0
  • p3p: CP="DSP ALL CUR ADMi DEVi CONi HISi OUR BUS NAV COM INT STA DEM LOC ONL PHY UNI"
  • x-powered-by: ASP.NET
  • x-aspnet-version: 4.0.30319
  • content-encoding: gzip
  • vary: Accept-Encoding
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for sportingbet.gr

DNS Analysis


DNS servers
ns2.netnames.net
ns1.netnames.net


DNS Records

Answer records
sportingbet.gr A 195.178.6.222 300s
sportingbet.gr NS  ns2.netnames.net 300s
sportingbet.gr NS  ns1.netnames.net 300s
sportingbet.gr SOA
server: ns1.netnames.net
email: hostmaster@netnames.net
serial: 2012121017
refresh: 162000
retry: 81000
expire: 1134000
minimum ttl: 538179
300s
sportingbet.gr MX
preference: 10
exchange: service113.mimecast.com
300s
sportingbet.gr MX
preference: 10
exchange: service114.mimecast.com
300s

Authority records

Additional records

IP 195.178.6.222 Analysis

  • Country Code
    EU
  • Country Code3
    EU
  • Country Name
    Europe
  • City
    EU
  • Continent Code
    47° North
  • Latitude
    8.
  • Longitude
  • No whois ip data for 195.178.6.222

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 31 Errors
  • 27 Warnings
Ratio Text/Html
  • 0.5054452740848662
Message Error
  • Error Line 79, Column 63: required attribute "alt" not specified
        <img src="/s/images/copyrightLogo.png" title="copyrightX"/>

    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 79, Column 63: document type does not allow element "img" here; assuming missing "object" start-tag
        <img src="/s/images/copyrightLogo.png" title="copyrightX"/>
  • Error Line 82, Column 8: end tag for "object" omitted, but OMITTAG NO was specified
    	</head>

    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 79, Column 5: start tag was here
        <img src="/s/images/copyrightLogo.png" title="copyrightX"/>
  • Warning Line 230, Column 7: multiple comments in comment declaration
    //------ The next three lines must be replaced for each country by those given …
  • Warning Line 230, Column 9: S separator in comment declaration
    //------ The next three lines must be replaced for each country by those given …

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 230, Column 10: invalid comment declaration: found name start character outside comment but inside comment declaration
    //------ The next three lines must be replaced for each country by those given …
  • Info Line 228, Column 54: comment declaration started here
    <script language="javascript" type="text/javascript"><!--
  • Warning Line 237, Column 9: character "&" is the first character of a delimiter but occurred as data
    .split("&"),i=0,l=a.length;i<l;i++){var p=a[i].indexOf("=");if(p>0)this.Q[a[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.
  • Error Line 237, Column 31: character ";" not allowed in attribute specification list
    .split("&"),i=0,l=a.length;i<l;i++){var p=a[i].indexOf("=");if(p>0)this.Q[a[i].…
  • Error Line 237, Column 31: element "l" undefined
    .split("&"),i=0,l=a.length;i<l;i++){var p=a[i].indexOf("=");if(p>0)this.Q[a[i].…

    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 238, Column 65: character ";" not allowed in attribute specification list
    …(var a=c.split(";"),i=0,b=a.length;i<b;i++){var v=a[i].split("=");while(v[0].s…
  • Warning Line 243, Column 74: character "&" is the first character of a delimiter but occurred as data
    …or(var n in this.A)if(this.A[n]!=null && this.A[n]!="")q+=(q.length>0?"&":(thi…

    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 243, Column 75: character "&" is the first character of a delimiter but occurred as data
    …r(var n in this.A)if(this.A[n]!=null && this.A[n]!="")q+=(q.length>0?"&":(this…

    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 243, Column 107: character "&" is the first character of a delimiter but occurred as data
    … this.A)if(this.A[n]!=null && this.A[n]!="")q+=(q.length>0?"&":(this.U.indexOf(

    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 244, Column 9: character "&" is the first character of a delimiter but occurred as data
    "?")>0?"&":"?"))+n+"="+escape(this.A[n]);return this.U+q;},SC:function(n,v,e,d)…

    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 246, Column 82: character "<" is the first character of a delimiter but occurred as data
    …dp=sld.split(".");var l=dp.length;if(l<2)sld=null;else if(!isNaN(dp[l-1])&&!is…

    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 246, Column 117: character "&" is the first character of a delimiter but occurred as data
    …sld.split(".");var l=dp.length;if(l<2)sld=null;else if(!isNaN(dp[l-1])&&!isNaN(

    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 246, Column 118: character "&" is the first character of a delimiter but occurred as data
    …sld.split(".");var l=dp.length;if(l<2)sld=null;else if(!isNaN(dp[l-1])&&!isNaN(

    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 247, Column 117: character "<" is the first character of a delimiter but occurred as data
    …p[l-1];return sld;},R:function(r,c,d,e){if(this.Enabled){var b=true;if(r<1000){

    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 248, Column 36: character ")" not allowed in attribute specification list
    b=(Math.floor(Math.random()*1000)<r);if(c!=null){if(this.C[c]!=null)b=(this.C[c…
  • Error Line 248, Column 36: element "r" undefined
    b=(Math.floor(Math.random()*1000)<r);if(c!=null){if(this.C[c]!=null)b=(this.C[c…

    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 249, Column 30: character "<" is the first character of a delimiter but occurred as data
    "mvt-no",e,d);}}if(b){var t='<'+this.ST+' src="'+this.S()+'"';for(n in this.SA)…

    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 249, Column 116: character "<" is the first character of a delimiter but occurred as data
    … src="'+this.S()+'"';for(n in this.SA)t+=(" "+n+'="'+this.SA[n]+'"');t+='><\/'+

    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 257, Column 84: character ";" not allowed in attribute specification list
    …(){for(var _i=0;_i<this.modules.length;_i++)optimost.displayModule(this.module…
  • Error Line 257, Column 84: element "this.modules.length" undefined
    …(){for(var _i=0;_i<this.modules.length;_i++)optimost.displayModule(this.module…

    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 258, Column 60: character "&" is the first character of a delimiter but occurred as data
    …f(this.url!=''){if((!this.trialCodeLow&&(typeof p!='string'||p!='low'))||(this…

    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 258, Column 61: character "&" is the first character of a delimiter but occurred as data
    …(this.url!=''){if((!this.trialCodeLow&&(typeof p!='string'||p!='low'))||(this.…

    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 258, Column 113: character "&" is the first character of a delimiter but occurred as data
    ….trialCodeLow&&(typeof p!='string'||p!='low'))||(this.trialCodeLow&&p=='low')){

    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 258, Column 115: cannot generate system identifier for general entity "p"
    ….trialCodeLow&&(typeof p!='string'||p!='low'))||(this.trialCodeLow&&p=='low')){

    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 258, Column 115: general entity "p" not defined and no default entity
    ….trialCodeLow&&(typeof p!='string'||p!='low'))||(this.trialCodeLow&&p=='low')){

    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 258, Column 116: reference not terminated by REFC delimiter
    ….trialCodeLow&&(typeof p!='string'||p!='low'))||(this.trialCodeLow&&p=='low')){

    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 258, Column 116: reference to entity "p" for which no system identifier could be generated
    ….trialCodeLow&&(typeof p!='string'||p!='low'))||(this.trialCodeLow&&p=='low')){

    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 258, Column 114: entity was defined here
    ….trialCodeLow&&(typeof p!='string'||p!='low'))||(this.trialCodeLow&&p=='low')){
  • Warning Line 260, Column 25: character "&" is the first character of a delimiter but occurred as data
    else if(this.hideCSS!=''&&(typeof p!='string'||p!='low')){document.write("<styl…

    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 260, Column 26: character "&" is the first character of a delimiter but occurred as data
    else if(this.hideCSS!=''&&(typeof p!='string'||p!='low')){document.write("<styl…

    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 260, Column 81: required attribute "type" not specified
    …ng'||p!='low')){document.write("<style>"+this.hideCSS+"</style>");if(this.show…

    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 266, Column 20: character "<" is the first character of a delimiter but occurred as data
    optrial=_ot;var t='<'+_o.ST+' src="'+_o.S()+'"';for(n in _o.SA)t+=(" "+n+'="'+_…

    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 266, Column 98: character "<" is the first character of a delimiter but occurred as data
    …or(n in _o.SA)t+=(" "+n+'="'+_o.SA[n]+'"');t+='><\/'+_o.ST+'>';_o.D.write(t)}};

    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 269, Column 20: character "&" is the first character of a delimiter but occurred as data
    opCDomain=='string'&&document.domain.indexOf(opCDomain)!=-1)return opCDomain;el…

    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 269, Column 22: cannot generate system identifier for general entity "document.domain.indexOf"
    opCDomain=='string'&&document.domain.indexOf(opCDomain)!=-1)return opCDomain;el…

    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 269, Column 22: general entity "document.domain.indexOf" not defined and no default entity
    opCDomain=='string'&&document.domain.indexOf(opCDomain)!=-1)return opCDomain;el…

    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 269, Column 45: reference not terminated by REFC delimiter
    …ain=='string'&&document.domain.indexOf(opCDomain)!=-1)return opCDomain;else re…

    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 269, Column 45: reference to entity "document.domain.indexOf" for which no system identifier could be generated
    …ain=='string'&&document.domain.indexOf(opCDomain)!=-1)return opCDomain;else 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.

  • Info Line 269, Column 21: entity was defined here
    opCDomain=='string'&&document.domain.indexOf(opCDomain)!=-1)return opCDomain;el…
  • Warning Line 274, Column 88: character "<" is the first character of a delimiter but occurred as data
    …etTime()/(3600000*24));document.write('<'+'script type="text/javascript" src="'

    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 275, Column 27: character "<" is the first character of a delimiter but occurred as data
    +opJsUrl+'?D_ds='+opDs+'"></'+'script>\n');

    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 276, Column 14: end tag for "this.modules.length" omitted, but OMITTAG NO was specified
    //--></script>

    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 257, Column 64: start tag was here
    …{};this.dMs=function(){for(var _i=0;_i<this.modules.length;_i++)optimost.displ…
  • Error Line 276, Column 14: end tag for "r" omitted, but OMITTAG NO was specified
    //--></script>

    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 248, Column 34: start tag was here
    b=(Math.floor(Math.random()*1000)<r);if(c!=null){if(this.C[c]!=null)b=(this.C[c…
  • Error Line 276, Column 14: end tag for "b" omitted, but OMITTAG NO was specified
    //--></script>

    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 238, Column 63: start tag was here
    …or(var a=c.split(";"),i=0,b=a.length;i<b;i++){var v=a[i].split("=");while(v[0]…
  • Error Line 276, Column 14: end tag for "l" omitted, but OMITTAG NO was specified
    //--></script>

    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 237, Column 29: start tag was here
    .split("&"),i=0,l=a.length;i<l;i++){var p=a[i].indexOf("=");if(p>0)this.Q[a[i].…
  • Error Line 280, Column 72: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"bt"><b></b></b><p id="tooltipcontent"></p><b class="bb"><b></b></b></span><di…

    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 309, Column 44: there is no attribute "data-code"
    			<a href="javascript:void(0);" data-code="el" >

    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 462, Column 28: character "&" is the first character of a delimiter but occurred as data
            if (langCode != '' && langCode != 'undefined' && langCode!='el') {

    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 462, Column 29: character "&" is the first character of a delimiter but occurred as data
            if (langCode != '' && langCode != 'undefined' && langCode!='el') {

    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 462, Column 55: character "&" is the first character of a delimiter but occurred as data
            if (langCode != '' && langCode != 'undefined' && langCode!='el') {

    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 462, Column 56: character "&" is the first character of a delimiter but occurred as data
            if (langCode != '' && langCode != 'undefined' && langCode!='el') {

    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 511, Column 13: ID "loginBox" already defined
    			<div id="loginBox">    

    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 509, Column 11: ID "loginBox" first defined here
    	<div id="loginBox" class="loginBox">
  • Error Line 527, Column 131: there is no attribute "placeholder"
    …me="username" type="text" maxlength="50" value=""  placeholder="Όνομα χρήστη"/>

    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 530, Column 119: there is no attribute "autocomplete"
    …wordField"  name="password" type="password" autocomplete="off" maxlength="50" >

    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 530, Column 141: end tag for "input" omitted, but OMITTAG NO was specified
    …wordField"  name="password" type="password" autocomplete="off" maxlength="50" >

    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 530, Column 17: start tag was here
                    <input id="modCustLoginPassword" class ="passwordField"  name="…
  • Error Line 534, Column 24: end tag for element "input" which is not open
                    </input>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 608, Column 159: ID "inplayhomelinkFlash" already defined
    …%87%ce%b7%ce%bc%ce%b1/5-0-1.html" id="inplayhomelinkFlash"><span>Liveplay cale…

    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 607, Column 155: ID "inplayhomelinkFlash" first defined here
    …f%cf%87%ce%b7%ce%bc%ce%b1/5.html" id="inplayhomelinkFlash"><span>Liveplay</spa…
  • Error Line 832, Column 50: end tag for "br" omitted, but OMITTAG NO was specified
             <a href="/t/casino/liveCasino.aspx"><br>Παίξε τώρα!</br></a>

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

  • Info Line 832, Column 46: start tag was here
             <a href="/t/casino/liveCasino.aspx"><br>Παίξε τώρα!</br></a>
  • Error Line 832, Column 65: end tag for element "br" which is not open
             <a href="/t/casino/liveCasino.aspx"><br>Παίξε τώρα!</br></a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 897, Column 47: there is no attribute "data-toggle"
                 	 <li class="opened" data-toggle="box">

    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 898, Column 42: there is no attribute "data-toggle"
    					<h4 class="innerHeader" data-toggle="head">Σημαντικότερα γεγονότα</h4>

    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 899, Column 39: there is no attribute "data-toggle"
    					<ul class="innerBox" data-toggle="body">

    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 957, Column 34: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<span class="currentTitle"><h3>Ολα στο πιάτο σου, μ' ένα απλό κλικ εδώ</h3><…

    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 960, Column 81: there is no attribute "linkindex"
    …ar-match-prices/9-746.html" linkindex="71">Δημοφιλείς αγώνες</a></b> & <b><a h…

    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 960, Column 112: character "&" is the first character of a delimiter but occurred as data
    …kindex="71">Δημοφιλείς αγώνες</a></b> & <b><a href="/sports-Πολλαπλά/most-popu…

    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 960, Column 276: element "marquee" undefined
    …στοιχηματικής αγοράς! <br/><b><marquee> Τσέκαρε και παίξε στη Νο1 εταιρεία δια…

    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 988, Column 34: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<span class="currentTitle"><h3>Πάρε μέρος στη μπασκετική δράση, κλικάροντας …

    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 991, Column 86: end tag for "br" omitted, but OMITTAG NO was specified
    …ι οι τέσσερις όμιλοι του Last-16, <br>ενώ εσύ ποντάρεις στο <b>νικητή</b> της …

    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 991, Column 82: start tag was here
    …6 και οι τέσσερις όμιλοι του Last-16, <br>ενώ εσύ ποντάρεις στο <b>νικητή</b> …
  • Error Line 1033, Column 34: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<span class="currentTitle"><h3>Τριάντα δύο (32) μονομάχοι διεκδικούν δεκαέξι…

    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 1078, Column 34: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<span class="currentTitle"><h3>Επέλεξε τους νικητές στα Grand Slam που έρχον…

    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 1137, Column 34: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<span class="currentTitle"><h3>Τρία παιχνίδια με τεράστια τζακπότ</h3></span>

    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 1154, Column 34: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<span class="currentTitle"><h3>Παίξε ζωντανή ρουλέτα με Έλληνες κρουπιέρηδες…

    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 1171, Column 34: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<span class="currentTitle"><h3>Παιχνίδια με πραγματικούς αντιπάλους</h3></sp…

    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 1246, Column 27: document type does not allow element "style" here
        <style type="text/css">

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

  • Warning Line 1266, Column 94: cannot generate system identifier for general entity "sports"
    …games/game.aspx?gameCode=ev-blackjack&sports', 'game', 'width=800,height=786,s…

    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 1266, Column 94: general entity "sports" not defined and no default entity
    …games/game.aspx?gameCode=ev-blackjack&sports', 'game', 'width=800,height=786,s…

    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 1266, Column 100: reference not terminated by REFC delimiter
    …game.aspx?gameCode=ev-blackjack&sports', 'game', 'width=800,height=786,statusb…

    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 1266, Column 100: reference to external entity in attribute value
    …game.aspx?gameCode=ev-blackjack&sports', 'game', 'width=800,height=786,statusb…

    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 1266, Column 100: reference to entity "sports" for which no system identifier could be generated
    …game.aspx?gameCode=ev-blackjack&sports', 'game', 'width=800,height=786,statusb…

    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 1266, Column 93: entity was defined here
    …/games/game.aspx?gameCode=ev-blackjack&sports', 'game', 'width=800,height=786,…
  • Warning Line 1269, Column 99: reference not terminated by REFC delimiter
    …/game.aspx?gameCode=ev-roulette&sports', 'game', 'width=800,height=786,statusb…

    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 1269, Column 99: reference to external entity in attribute value
    …/game.aspx?gameCode=ev-roulette&sports', 'game', 'width=800,height=786,statusb…

    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 1269, Column 99: reference to entity "sports" for which no system identifier could be generated
    …/game.aspx?gameCode=ev-roulette&sports', 'game', 'width=800,height=786,statusb…

    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 1266, Column 93: entity was defined here
    …/games/game.aspx?gameCode=ev-blackjack&sports', 'game', 'width=800,height=786,…
  • Error Line 1423, Column 7: 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>.

  • Error Line 1423, Column 7: document type does not allow element "style" here
    <style>

    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 1439, Column 23: there is no attribute "data-showonly"
    				<ul data-showonly="1 vertical" class="hide">

    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 1441, Column 110: reference not terminated by REFC delimiter
    …/game.aspx?gameCode=ga-roulette&sports', 'game', 'width=750,height=662,statusb…

    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 1441, Column 110: reference to external entity in attribute value
    …/game.aspx?gameCode=ga-roulette&sports', 'game', 'width=750,height=662,statusb…

    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 1441, Column 110: reference to entity "sports" for which no system identifier could be generated
    …/game.aspx?gameCode=ga-roulette&sports', 'game', 'width=750,height=662,statusb…

    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 1266, Column 93: entity was defined here
    …/games/game.aspx?gameCode=ev-blackjack&sports', 'game', 'width=800,height=786,…
  • Warning Line 1446, Column 113: reference not terminated by REFC delimiter
    …me.aspx?gameCode=ng-jackhammer2&sports', 'game', 'width=643,height=603,statusb…

    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 1446, Column 113: reference to external entity in attribute value
    …me.aspx?gameCode=ng-jackhammer2&sports', 'game', 'width=643,height=603,statusb…

    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 1446, Column 113: reference to entity "sports" for which no system identifier could be generated
    …me.aspx?gameCode=ng-jackhammer2&sports', 'game', 'width=643,height=603,statusb…

    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 1266, Column 93: entity was defined here
    …/games/game.aspx?gameCode=ev-blackjack&sports', 'game', 'width=800,height=786,…
  • Warning Line 1457, Column 115: reference not terminated by REFC delimiter
    ….aspx?gameCode=ga-pro-blackjack&sports', 'game', 'width=750,height=662,statusb…

    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 1457, Column 115: reference to external entity in attribute value
    ….aspx?gameCode=ga-pro-blackjack&sports', 'game', 'width=750,height=662,statusb…

    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 1457, Column 115: reference to entity "sports" for which no system identifier could be generated
    ….aspx?gameCode=ga-pro-blackjack&sports', 'game', 'width=750,height=662,statusb…

    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 1266, Column 93: entity was defined here
    …/games/game.aspx?gameCode=ev-blackjack&sports', 'game', 'width=800,height=786,…
  • Error Line 1492, Column 5: end tag for "ul" which is not finished
    </ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 1518, Column 48: end tag for "ul" which is not finished
          <ul id="ulLiveNow" class="header-ul"></ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 1929, Column 46: there is no attribute "data-roundcorner"
    		<div class="containerBox" data-roundcorner="2" style="width:300px;">

    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 1939, Column 82: there is no attribute "data-roundcorner"
    …class="containerBox" data-roundcorner="2" style="width:679px; margin-left:-186…

    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 1940, Column 7: document type does not allow element "ul" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<ul>

    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 2009, 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>.

  • Error Line 2009, Column 8: document type does not allow element "script" here
    <script>

    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
  • 8.750 visits