Errors found while checking this document as HTML 4.01 Transitional!

Result: 17 Errors, 4 warning(s)
:
: utf-8
: HTML 4.01 Transitional
Root Element: html
Options

Help on the options is available.

Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.

  1. Warning Unable to Determine Parse Mode!

    The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:

    • the MIME Media Type (text/html) can be used for XML or SGML document types
    • No known Document Type could be detected
    • No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
    • No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.

    As a default, the validator is falling back to SGML mode.

  2. Warning No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.

    No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.

    The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.

    Learn how to add a doctype to your document from our FAQ.

↑ Top

Validation Output: 17 Errors

  1. Error Line 5, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html data-adblockkey="MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBAKX74ixpzVyXbJprcLfbH4ps…

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  2. Error Line 5, Column 23: there is no attribute "DATA-ADBLOCKKEY"
    <html data-adblockkey="MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBAKX74ixpzVyXbJprcLfbH4ps…

    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.

  3. Error Line 37, Column 110: end tag for "HEAD" which is not finished
    …=1';}catch(exception){}</script></head><frameset rows="100%,*" frameborder="no…

    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.

  4. Error Line 37, Column 126: there is no attribute "ROWS"
    …tion){}</script></head><frameset rows="100%,*" frameborder="no" border="0" fra…

    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.

  5. Error Line 37, Column 147: there is no attribute "FRAMEBORDER"
    …pt></head><frameset rows="100%,*" frameborder="no" border="0" framespacing="0">

    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.

  6. Error Line 37, Column 159: there is no attribute "BORDER"
    …pt></head><frameset rows="100%,*" frameborder="no" border="0" framespacing="0">

    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.

  7. Error Line 37, Column 176: there is no attribute "FRAMESPACING"
    …pt></head><frameset rows="100%,*" frameborder="no" border="0" framespacing="0">

    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.

  8. Error Line 37, Column 179: element "FRAMESET" undefined
    …pt></head><frameset rows="100%,*" frameborder="no" border="0" framespacing="0">

    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).
  9. Error Line 38, Column 13: there is no attribute "SRC"
    	<frame src="http://www.nova.coop/?fp=NGpkEXWxlO7BrVgukEDj1AMtJ2EGFrwokgOyLtsxE…

    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.

  10. Warning Line 38, Column 136: cannot generate system identifier for general entity "prvtof"
    …2FHD%2FE1wlUPRkEyLk6wHWpmPP1r6w%3D%3D&prvtof=oOQv%2FDfcE9iF3o%2FN8rVyz2h5tjH9H…

    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.

  11. Error Line 38, Column 136: general entity "prvtof" not defined and no default entity
    …2FHD%2FE1wlUPRkEyLk6wHWpmPP1r6w%3D%3D&prvtof=oOQv%2FDfcE9iF3o%2FN8rVyz2h5tjH9H…

    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.

  12. Error Line 38, Column 142: reference to entity "prvtof" for which no system identifier could be generated
    …FE1wlUPRkEyLk6wHWpmPP1r6w%3D%3D&prvtof=oOQv%2FDfcE9iF3o%2FN8rVyz2h5tjH9HaxE56h…

    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.

  13. Info Line 38, Column 135: entity was defined here
    …%2FHD%2FE1wlUPRkEyLk6wHWpmPP1r6w%3D%3D&prvtof=oOQv%2FDfcE9iF3o%2FN8rVyz2h5tjH9…
  14. Warning Line 38, Column 196: cannot generate system identifier for general entity "poru"
    …o%2FN8rVyz2h5tjH9HaxE56hDzz1q0%2Fc%3D&poru=K5q2EJt3Sml0cXm6Mkeqoma08GOA8Itpi%2…

    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.

  15. Error Line 38, Column 196: general entity "poru" not defined and no default entity
    …o%2FN8rVyz2h5tjH9HaxE56hDzz1q0%2Fc%3D&poru=K5q2EJt3Sml0cXm6Mkeqoma08GOA8Itpi%2…

    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.

  16. Error Line 38, Column 200: reference to entity "poru" for which no system identifier could be generated
    …N8rVyz2h5tjH9HaxE56hDzz1q0%2Fc%3D&poru=K5q2EJt3Sml0cXm6Mkeqoma08GOA8Itpi%2B0MB…

    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.

  17. Info Line 38, Column 195: entity was defined here
    …3o%2FN8rVyz2h5tjH9HaxE56hDzz1q0%2Fc%3D&poru=K5q2EJt3Sml0cXm6Mkeqoma08GOA8Itpi%…
  18. Error Line 38, Column 271: element "FRAME" undefined
    …3D&poru=K5q2EJt3Sml0cXm6Mkeqoma08GOA8Itpi%2B0MB5jmO1uX%2F7bTxqu8fNkLQ7TeSRB0&">

    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).
  19. Error Line 41, Column 40: document type does not allow element "BODY" here
    	<body bgcolor="#ffffff" text="#000000">

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

  20. Error Line 42, Column 139: reference to entity "prvtof" for which no system identifier could be generated
    …FE1wlUPRkEyLk6wHWpmPP1r6w%3D%3D&prvtof=%2Fj%2FFMQLY77k%2BMRCPmVi3T01FxtcUMerXk…

    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.

  21. Info Line 38, Column 135: entity was defined here
    …%2FHD%2FE1wlUPRkEyLk6wHWpmPP1r6w%3D%3D&prvtof=oOQv%2FDfcE9iF3o%2FN8rVyz2h5tjH9…
  22. Error Line 42, Column 197: reference to entity "poru" for which no system identifier could be generated
    …RCPmVi3T01FxtcUMerXkOwAPrPHDQg%3D&poru=%2BrUUnkhvW8hOgwlv19hUzHIknabDUy8kw4Rzy…

    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.

  23. Info Line 38, Column 195: entity was defined here
    …3o%2FN8rVyz2h5tjH9HaxE56hDzz1q0%2Fc%3D&poru=K5q2EJt3Sml0cXm6Mkeqoma08GOA8Itpi%…

↑ Top