staatsloterij.nl

De Staatsloterij is dé loterij van Nederland, met de meeste kans op de grootste prijzen. ...

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

Overview Info

  • Domain Name
    staatsloterij.nl
  • Favicon
  • Alexa Rank
    #42643
  • Google Page Rank
    PR 5
  • Ip Address
    62.21.128.215
  • Page Size
    18.6 KB
  • Images
    1 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 3 1 0 0

Website Meta Analysis



  • Title
    Staatsloterij - de prijzenloterij van Nederland
  • Meta Keyword
    staatsloterij, staatslot, trekking, jackpot
  • Meta Description
    De Staatsloterij is dé loterij van Nederland, met de meeste kans op de grootste prijzen.

Technical Analysis



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

Hyper Text Transfer Protocol (HTTP) header show data header response from staatsloterij.nl.

HTML Analysis

  • server: Microsoft-IIS/6.0
  • x-powered-by: Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0
  • expires: Sat, 6 May 1995 12:00:00 GMT
  • cache-control: no-store, must-revalidate, post-check=0, pre-check=0
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-type: text/html;charset=UTF-8
  • content-length: 5065
  • accept-ranges: bytes
  • date: Wed, 18 Sep 2013 17:11:29 GMT
  • x-varnish: 1863529701 1863528399
  • age: 49
  • via: 1.1 varnish
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
No data whois for staatsloterij.nl

DNS Analysis


DNS servers
nsgbr.comlaude.co.uk [212.95.244.211]
nssui.comlaude.ch
nsusa.comlaude.net [64.147.99.10]


DNS Records

Answer records
staatsloterij.nl SOA
server: nsgbr.comlaude.co.uk
email: hostmaster@comlaude.com
serial: 2013012362
refresh: 86400
retry: 7200
expire: 2419200
minimum ttl: 3600
300s
staatsloterij.nl NS  nssui.comlaude.ch 300s
staatsloterij.nl NS  nsgbr.comlaude.co.uk 300s
staatsloterij.nl NS  nsusa.comlaude.net 300s
staatsloterij.nl TXT google-site-verification=4Ue0JCKlmnaI7GucV1qggKi5-vF4Olw1bqNWH0Sbj1A 300s
staatsloterij.nl TXT v=spf1 mx ip4:62.21.128.192/27 -all 300s
staatsloterij.nl MX
preference: 10
exchange: mail.intralotnetherlands.nl
300s
staatsloterij.nl A 62.21.128.215 300s

Authority records

Additional records
nsgbr.comlaude.co.uk A 212.95.244.211 172800s
nssui.comlaude.ch A 213.160.89.226 172800s
nsusa.comlaude.net A 64.147.99.10 86400s

IP 62.21.128.215 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 59 Errors
  • 36 Warnings
Ratio Text/Html
  • 0.6066505314111333
Message Error
  • Error Line 26, Column 77: "async" is not a member of a group specified for any attribute
    …'//d3c3cq33003psk.cloudfront.net/opentag-67008-473432.js' async defer></script>
  • Error Line 26, Column 82: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …'//d3c3cq33003psk.cloudfront.net/opentag-67008-473432.js' async defer></script>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 26, Column 82: required attribute "type" not specified
    …'//d3c3cq33003psk.cloudfront.net/opentag-67008-473432.js' async defer></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 29, Column 12: there is no attribute "NAME"
    <META NAME="Title" CONTENT='Staatsloterij - Dé loterij van Nederland'>

    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 29, Column 28: there is no attribute "CONTENT"
    <META NAME="Title" CONTENT='Staatsloterij - Dé loterij van Nederland'>

    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 29, Column 70: element "META" undefined
    <META NAME="Title" CONTENT='Staatsloterij - Dé loterij van Nederland'>

    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 30, Column 124: element "META" undefined
    …terij is dé loterij van Nederland, met de meeste kans op de grootste prijzen.'>

    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 31, Column 76: element "META" undefined
    <META NAME="KEYWORDS" CONTENT='staatsloterij, staatslot, trekking, jackpot'>

    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 32, Column 44: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="robots" content="INDEX,FOLLOW">

    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 32, Column 1: start tag was here
    <meta name="robots" content="INDEX,FOLLOW">
  • Error Line 36, Column 18: there is no attribute "language"
    <script language="JavaScript" src="/cspublish/Staatsloterij/script/jquery.pack.…

    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 55, Column 28: end tag for "META" omitted, but OMITTAG NO was specified
    <!-- Mopinion end --></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 31, Column 1: start tag was here
    <META NAME="KEYWORDS" CONTENT='staatsloterij, staatslot, trekking, jackpot'>
  • Error Line 55, Column 28: end tag for "META" omitted, but OMITTAG NO was specified
    <!-- Mopinion end --></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 30, Column 1: start tag was here
    <META NAME="Description" CONTENT='De Staatsloterij is dé loterij van Nederland,…
  • Error Line 55, Column 28: end tag for "META" omitted, but OMITTAG NO was specified
    <!-- Mopinion end --></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 29, Column 1: start tag was here
    <META NAME="Title" CONTENT='Staatsloterij - Dé loterij van Nederland'>
  • Error Line 55, Column 28: end tag for "head" which is not finished
    <!-- Mopinion end --></head>

    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 119, 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 135, Column 38: character ";" not allowed in attribute specification list
    	for (var i = 0; i<labelValues.length; i++) {
  • Error Line 135, Column 38: element "labelValues.length" undefined
    	for (var i = 0; i<labelValues.length; 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).
  • Warning Line 169, Column 38: character "&" is the first character of a delimiter but occurred as data
    	}else if($("#password").val() != "" && ($("#username").val() == "" || $("#user…

    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 169, Column 39: character "&" is the first character of a delimiter but occurred as data
    	}else if($("#password").val() != "" && ($("#username").val() == "" || $("#user…

    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 228, Column 9: end tag for "labelValues.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 135, Column 19: start tag was here
    	for (var i = 0; i<labelValues.length; i++) {
  • Error Line 243, Column 14: there is no attribute "align"
    		<div align="right"    id="wwctrl_loginBtn"><input type="submit" id="loginBtn"…

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

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

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

  • Error Line 246, Column 115: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …edURL" value="/stl/mijnStaats.html;jsessionid=uNJoty+vbSUoSSWjflZDUA**.node9"/>

    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 273, 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 298, Column 3: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><span class="arrow">&nbsp;</span><strong>Koop Staatslot</strong></p>

    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 302, Column 162: there is no attribute "target"
    …1245164629218&amp;p=1221558155870&amp;pagename=StaatsWrapper" target="_blank" >

    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 308, Column 3: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><span class="arrow">&nbsp;</span><strong>Ga automatisch meespelen</strong></…

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

  • Warning Line 322, Column 151: cannot generate system identifier for general entity "pagename"
    …ref="/cspublish/Satellite?c=Content_C&pagename=Staatsloterij%2FContent_C%2FSta…

    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 322, Column 151: general entity "pagename" not defined and no default entity
    …ref="/cspublish/Satellite?c=Content_C&pagename=Staatsloterij%2FContent_C%2FSta…

    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 322, Column 159: reference not terminated by REFC delimiter
    …publish/Satellite?c=Content_C&pagename=Staatsloterij%2FContent_C%2FStaatsDetai…

    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 322, Column 159: reference to external entity in attribute value
    …publish/Satellite?c=Content_C&pagename=Staatsloterij%2FContent_C%2FStaatsDetai…

    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 322, Column 159: reference to entity "pagename" for which no system identifier could be generated
    …publish/Satellite?c=Content_C&pagename=Staatsloterij%2FContent_C%2FStaatsDetai…

    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 322, Column 150: entity was defined here
    …href="/cspublish/Satellite?c=Content_C&pagename=Staatsloterij%2FContent_C%2FSt…
  • Warning Line 322, Column 201: cannot generate system identifier for general entity "cid"
    …atsloterij%2FContent_C%2FStaatsDetail&cid=1244308228685" style="cursor: pointe…

    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 322, Column 201: general entity "cid" not defined and no default entity
    …atsloterij%2FContent_C%2FStaatsDetail&cid=1244308228685" style="cursor: pointe…

    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 322, Column 204: reference not terminated by REFC delimiter
    …loterij%2FContent_C%2FStaatsDetail&cid=1244308228685" style="cursor: pointer;"…

    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 322, Column 204: reference to external entity in attribute value
    …loterij%2FContent_C%2FStaatsDetail&cid=1244308228685" style="cursor: pointer;"…

    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 322, Column 204: reference to entity "cid" for which no system identifier could be generated
    …loterij%2FContent_C%2FStaatsDetail&cid=1244308228685" style="cursor: pointer;"…

    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 322, Column 200: entity was defined here
    …aatsloterij%2FContent_C%2FStaatsDetail&cid=1244308228685" style="cursor: point…
  • Warning Line 323, Column 48: cannot generate system identifier for general entity "blobkey"
    …"/cspublish/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwher…

    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 323, Column 48: general entity "blobkey" not defined and no default entity
    …"/cspublish/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwher…

    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 323, Column 55: reference not terminated by REFC delimiter
    …lish/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=12697…

    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 323, Column 55: reference to external entity in attribute value
    …lish/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=12697…

    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 323, Column 55: reference to entity "blobkey" for which no system identifier could be generated
    …lish/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=12697…

    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 323, Column 47: entity was defined here
    …="/cspublish/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 323, Column 59: cannot generate system identifier for general entity "blobtable"
    …/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=126976343…

    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 323, Column 59: general entity "blobtable" not defined and no default entity
    …/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=126976343…

    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 323, Column 68: reference not terminated by REFC delimiter
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbi…

    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 323, Column 68: reference to external entity in attribute value
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbi…

    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 323, Column 68: reference to entity "blobtable" for which no system identifier could be generated
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbi…

    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 323, Column 58: entity was defined here
    …h/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=12697634…
  • Warning Line 323, Column 80: cannot generate system identifier for general entity "blobwhere"
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">

    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 323, Column 80: general entity "blobwhere" not defined and no default entity
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">

    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 323, Column 89: reference not terminated by REFC delimiter
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">

    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 323, Column 89: reference to external entity in attribute value
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">

    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 323, Column 89: reference to entity "blobwhere" for which no system identifier could be generated
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">

    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 323, Column 79: entity was defined here
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">
  • Warning Line 323, Column 104: cannot generate system identifier for general entity "ssbinary"
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">

    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 323, Column 104: general entity "ssbinary" not defined and no default entity
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">

    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 323, Column 112: reference not terminated by REFC delimiter
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">

    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 323, Column 112: reference to external entity in attribute value
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">

    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 323, Column 112: reference to entity "ssbinary" for which no system identifier could be generated
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">

    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 323, Column 103: entity was defined here
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">
  • Error Line 323, Column 118: required attribute "alt" not specified
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">

    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 323, Column 119: end tag for "img" omitted, but OMITTAG NO was specified
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">

    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 323, Column 1: start tag was here
    <img src="/cspublish/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&…
  • Warning Line 327, Column 55: reference not terminated by REFC delimiter
    …lish/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=12697…

    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 327, Column 55: reference to external entity in attribute value
    …lish/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=12697…

    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 327, Column 55: reference to entity "blobkey" for which no system identifier could be generated
    …lish/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=12697…

    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 323, Column 47: entity was defined here
    …="/cspublish/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 327, Column 68: reference not terminated by REFC delimiter
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763684637&ssbi…

    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 327, Column 68: reference to external entity in attribute value
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763684637&ssbi…

    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 327, Column 68: reference to entity "blobtable" for which no system identifier could be generated
    …e?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763684637&ssbi…

    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 323, Column 58: entity was defined here
    …h/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=12697634…
  • Warning Line 327, Column 89: reference not terminated by REFC delimiter
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763684637&ssbinary=true">

    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 327, Column 89: reference to external entity in attribute value
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763684637&ssbinary=true">

    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 327, Column 89: reference to entity "blobwhere" for which no system identifier could be generated
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763684637&ssbinary=true">

    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 323, Column 79: entity was defined here
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">
  • Warning Line 327, Column 112: reference not terminated by REFC delimiter
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763684637&ssbinary=true">

    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 327, Column 112: reference to external entity in attribute value
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763684637&ssbinary=true">

    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 327, Column 112: reference to entity "ssbinary" for which no system identifier could be generated
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763684637&ssbinary=true">

    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 323, Column 103: entity was defined here
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763436530&ssbinary=true">
  • Error Line 327, Column 118: required attribute "alt" not specified
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763684637&ssbinary=true">

    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 327, Column 119: end tag for "img" omitted, but OMITTAG NO was specified
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1269763684637&ssbinary=true">

    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 327, Column 1: start tag was here
    <img src="/cspublish/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&…
  • Error Line 328, Column 19: end tag for "br" omitted, but OMITTAG NO was specified
    <p>De volgende<br>trekking is op

    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 328, Column 15: start tag was here
    <p>De volgende<br>trekking is op
  • Error Line 329, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 329, Column 1: start tag was here
    <br>
  • Error Line 338, Column 3: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><span class="arrow">&nbsp;</span><strong>Staatsloten kopen</strong></p>

    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 340, Column 3: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><span class="arrow">&nbsp;</span><strong>Automatisch meespelen</strong></p>

    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 342, Column 3: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><span class="arrow">&nbsp;</span><strong>Meespelen met een groep</strong></p>

    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 358, Column 12: 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 395, Column 24: there is no attribute "contenteditable"
    <li><a contenteditable="false" href="/DutchLotteriesStaatsWeb/viewFaqCategory.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 415, Column 26: character "&" is the first character of a delimiter but occurred as data
    <span class="link">Adres & Routebeschrijving</span>

    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 422, Column 52: element "u" undefined
    …ublish/Satellite/Staats/disclaimer"><u>Disclaimer</u></a>&nbsp;&nbsp;|&nbsp;&n…

    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 422, Column 156: element "u" undefined
    …tellite/Staats/deelnemersreglement"><u>Deelnemersreglement</u></a> &nbsp;&nbsp…

    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 422, Column 258: element "u" undefined
    …cspublish/Satellite/Staats/privacy"><u>Privacy</u></a>&nbsp;&nbsp;|&nbsp;&nbsp…

    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 422, Column 463: element "u" undefined
    …7747154&amp;pagename=StaatsWrapper"><u>Cookies</u></a>&nbsp;&nbsp;|&nbsp;&nbsp…

    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 422, Column 572: element "u" undefined
    …estaatsloterij.nl/" target="_blank"><u>Vacatures</u></a> &nbsp;&nbsp;|&nbsp;&n…

    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 422, Column 780: element "u" undefined
    …8287950&amp;pagename=StaatsWrapper"><u>Verkooppunten</u></a> &nbsp;&nbsp;|&nbs…

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

Visitor Analysis

Daily Visitor
  • 10.383 visits

In Page Analysis