PCH Search & Win is a powerful search engine with a twist! Each search gives you a chance to win a prize sweepstakes instantly. No registration required. ...

pchsearch.com
  • Domain Name
    pchsearch.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #68874
  • Page Size
    12.5 KB
  • Ip Address
    164.109.16.222
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Instant Win Prizes from Searching, Free Online Sweepstakes | PCHSearchAndWin
  • Meta Keyword
    search and win, search and win prizes,search engine sweepstakes,search metacrawler
  • Meta Description
    PCH Search & Win is a powerful search engine with a twist! Each search gives you a chance to win a prize sweepstakes instantly. No registration required.

Technical Analysis

  • Webserver
    Apache/2.2.3 (Red Hat)
  • Ip Address
    164.109.16.222
  • Domain Age
    9 Years, 9 Months, 0 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Tue, 30 Jul 2013 15:07:30 GMT
  • server: Apache/2.2.3 (Red Hat)
  • cache-control: max-age=0
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 4686
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Publishers Clearing House
382 Channel Drive
Port Washington, NY 11050
US

Domain Name: PCHSEARCH.COM



Administrative Contact:
Publishers Clearing House email
382 Channel Drive
Port Washington, NY 11050
US
516-883-5432 fax: 123 123 1234

Technical Contact:
Network Solutions, LLC. email
13861 Sunrise Valley Drive
Herndon, VA 20171
US
1-888-642-9675 fax: 571-434-4620

Record expires on 21-Oct-2014.
Record created on 21-Oct-2003.
Database last updated on 18-Sep-2012 23:40:49 EDT.

Domain servers in listed order:

NS1.PCH.COM 216.255.103.232
MIA03.DIGEX.COM 216.255.129.246

DNS Analysis


DNS servers
ns1.pch.com [216.255.103.232]
mia03.digex.com [216.255.129.246]


DNS Records

Answer records
pchsearch.com SOA
server: ns1.pch.com
email: hostmaster
serial: 57
refresh: 900
retry: 600
expire: 86400
minimum ttl: 3600
600s
pchsearch.com A 164.109.16.222 3600s
pchsearch.com NS  mia03-1.digex.com 3600s
pchsearch.com NS  ns1.pch.com 3600s
pchsearch.com MX
preference: 10
exchange: av2.pchmail.com
3600s
pchsearch.com TXT spf2.0/pra ip4:69.228.175.125 ip4:207.97.206.18 ip4:207.97.206.19 ip4:207.97.206.20 ip4:207.97.206.21 ip4:207.97.206.22 ip4:207.97.220.36 -all 3600s

Authority records

Additional records

IP 164.109.16.222 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Beltsville
  • Continent Code
    20705
  • Latitude
    301
  • Longitude
    511
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 164.109.16.222"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=164.109.16.222?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 164.109.0.0 - 164.109.255.255
    CIDR: 164.109.0.0/16
    OriginAS:
    NetName: DIGEX-BLK3
    NetHandle: NET-164-109-0-0-1
    Parent: NET-164-0-0-0-0
    NetType: Direct Allocation
    RegDate: 1993-02-18
    Updated: 2012-03-20
    Ref: http://whois.arin.net/rest/net/NET-164-109-0-0-1

    OrgName: MCI Communications Services, Inc. d/b/a Verizon Business
    OrgId: MCICS
    Address: 22001 Loudoun County Pkwy
    City: Ashburn
    StateProv: VA
    PostalCode: 20147
    Country: US
    RegDate: 2006-05-30
    Updated: 2011-11-30
    Ref: http://whois.arin.net/rest/org/MCICS

    OrgTechHandle: SWIPP-ARIN
    OrgTechName: swipper
    OrgTechPhone: +1-800-900-0241
    OrgTechEmail: swipper@verizonbusiness.com
    OrgTechRef: http://whois.arin.net/rest/poc/SWIPP-ARIN

    OrgNOCHandle: OA12-ARIN
    OrgNOCName: UUnet Technologies, Inc., Technologies
    OrgNOCPhone: +1-800-900-0241
    OrgNOCEmail: help4u@verizonbusiness.com
    OrgNOCRef: http://whois.arin.net/rest/poc/OA12-ARIN

    OrgAbuseHandle: ABUSE3-ARIN
    OrgAbuseName: abuse
    OrgAbusePhone: +1-800-900-0241
    OrgAbuseEmail: abuse-mail@verizonbusiness.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/ABUSE3-ARIN

    OrgTechHandle: JHU140-ARIN
    OrgTechName: Huffines, Jody
    OrgTechPhone: +1-703-886-6093
    OrgTechEmail: Jody.Huffines@one.verizon.com
    OrgTechRef: http://whois.arin.net/rest/poc/JHU140-ARIN

    OrgTechHandle: SWIPP9-ARIN
    OrgTechName: SWIPPER
    OrgTechPhone: +1-800-900-0241
    OrgTechEmail: swipper@verizon.com
    OrgTechRef: http://whois.arin.net/rest/poc/SWIPP9-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 55 Errors
  • 25 Warnings
Ratio Text/Html
  • 0.4700468018720749
Message Error
  • Warning Line 5, Column 103: NET-enabling start-tag requires SHORTTAG YES
    …on" href="http://static.blingo.com/shared/mobile/img/touch-icon-iphone_.png" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 5, Column 104: character data is not allowed here
    …on" href="http://static.blingo.com/shared/mobile/img/touch-icon-iphone_.png" />

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 6, Column 36: there is no attribute "SIZES"
    <link rel="apple-touch-icon" sizes="72x72" href="http://static.blingo.com/share…

    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 6, Column 115: NET-enabling start-tag requires SHORTTAG YES
    …2x72" href="http://static.blingo.com/shared/mobile/img/touch-icon-ipad_.png" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 7, Column 120: NET-enabling start-tag requires SHORTTAG YES
    …4" href="http://static.blingo.com/shared/mobile/img/touch-icon-iphone4_.png" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 19, Column 107: end tag for element "STRONG" which is not open
    …cess to PCHSearchWin! Tap %icon and then <strong>Add to Home Screen</strong>.' 

    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.

  • Warning Line 25, Column 100: NET-enabling start-tag requires SHORTTAG YES
    …" href="http://static.blingo.com/version/117/shared/mobile/css/add2home.css" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 25, Column 101: character data is not allowed here
    …" href="http://static.blingo.com/version/117/shared/mobile/css/add2home.css" />

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 27, Column 81: required attribute "TYPE" not specified
    …="http://cdn.pch.com/spectrum/mobile/js/pchDeviceDetection.v2.min.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 28, 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 55, Column 16: there is no attribute "PROPERTY"
    <meta property="og:title" content="PCHSearchAndWin"/>

    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 55, Column 52: NET-enabling start-tag requires SHORTTAG YES
    <meta property="og:title" content="PCHSearchAndWin"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 55, Column 53: character data is not allowed here
    <meta property="og:title" content="PCHSearchAndWin"/>

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 56, Column 43: NET-enabling start-tag requires SHORTTAG YES
    <meta property="og:type" content="website"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 57, Column 56: NET-enabling start-tag requires SHORTTAG YES
    <meta property="og:url" content="http://search.pch.com"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 58, Column 105: NET-enabling start-tag requires SHORTTAG YES
    …ontent="http://static.blingo.com/shared/images/fbpreview/clickthensearch.gif"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 59, Column 104: NET-enabling start-tag requires SHORTTAG YES
    …content="http://static.blingo.com/shared/images/fbpreview/searchandenter.gif"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 60, Column 99: NET-enabling start-tag requires SHORTTAG YES
    …age" content="http://static.blingo.com/shared/images/fbpreview/thisisbig.gif"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 61, Column 99: NET-enabling start-tag requires SHORTTAG YES
    …age" content="http://static.blingo.com/shared/images/fbpreview/todayonly.gif"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 62, Column 102: NET-enabling start-tag requires SHORTTAG YES
    …" content="http://static.blingo.com/shared/images/fbpreview/winnerstoday.gif"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 63, Column 197: NET-enabling start-tag requires SHORTTAG YES
    …ou a chance to win a prize sweepstakes instantly.  No registration required."/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 66, 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 72, Column 66: required attribute "TYPE" not specified
    <script src="http://static.blingo.com/shared/jquery-1.4.2.min.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 73, Column 65: required attribute "TYPE" not specified
    <script src="http://static.blingo.com/shared/shelf/js/action.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 76, 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 110, 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 125, Column 8: required attribute "TYPE" not specified
    <script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 135, Column 51: cannot generate system identifier for general entity "c2"
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 135, Column 51: general entity "c2" not defined and no default entity
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Error Line 135, Column 53: reference to entity "c2" for which no system identifier could be generated
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 135, Column 50: entity was defined here
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />
  • Warning Line 135, Column 62: cannot generate system identifier for general entity "cv"
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 135, Column 62: general entity "cv" not defined and no default entity
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Error Line 135, Column 64: reference to entity "cv" for which no system identifier could be generated
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 135, Column 61: entity was defined here
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />
  • Warning Line 135, Column 69: cannot generate system identifier for general entity "cj"
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 135, Column 69: general entity "cj" not defined and no default entity
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Error Line 135, Column 71: reference to entity "cj" for which no system identifier could be generated
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 135, Column 68: entity was defined here
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />
  • Warning Line 135, Column 75: NET-enabling start-tag requires SHORTTAG YES
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 135, Column 75: required attribute "ALT" not specified
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />

    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 75: document type does not allow element "IMG" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "DIV", "ADDRESS" start-tag
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />

    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 135, Column 76: character data is not allowed here
      <img src="http://b.scorecardresearch.com/p?c1=2&c2=8431438&cv=2.0&cj=1" />

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 136, Column 11: end tag for "NOSCRIPT" which is not finished
    </noscript>

    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 140, 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 176, Column 7: end tag for element "HEAD" which is not open
    </head>

    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 177, Column 6: document type does not allow element "BODY" here
    <body>

    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 191, Column 21: end tag for element "LI" which is not open
                    </li>

    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 193, Column 45: there is no attribute "TARGET"
    …          <li><a href="/rules" target="_blank">Official Rules</a>&nbsp;/&nbsp;…

    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 197, Column 70: cannot generate system identifier for general entity "Win"
    …              <li><a href="/about" target="_blank">About PCHSearch&Win</a></li>

    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 197, Column 70: general entity "Win" not defined and no default entity
    …              <li><a href="/about" target="_blank">About PCHSearch&Win</a></li>

    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.

  • Error Line 197, Column 73: reference to entity "Win" for which no system identifier could be generated
    …              <li><a href="/about" target="_blank">About PCHSearch&Win</a></li>

    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 197, Column 69: entity was defined here
    …              <li><a href="/about" target="_blank">About PCHSearch&Win</a></li>
  • Error Line 203, Column 87: required attribute "TYPE" not specified
    …ect.facebook.net/en_US/all.js#xfbml=1"></script><fb:like href="http://www.face…

    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 203, Column 111: there is no attribute "HREF"
    …ll.js#xfbml=1"></script><fb:like href="http://www.facebook.com/PCHSearchAndWin…

    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 203, Column 158: there is no attribute "SEND"
    …ww.facebook.com/PCHSearchAndWin" send="true" layout="button_count" show_faces=…

    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 203, Column 172: there is no attribute "LAYOUT"
    …m/PCHSearchAndWin" send="true" layout="button_count" show_faces="false" font="…

    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 203, Column 198: there is no attribute "SHOW_FACES"
    …send="true" layout="button_count" show_faces="false" font="verdana" ></fb:like>

    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 203, Column 211: there is no attribute "FONT"
    …send="true" layout="button_count" show_faces="false" font="verdana" ></fb:like>

    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 203, Column 221: element "FB:LIKE" undefined
    …send="true" layout="button_count" show_faces="false" font="verdana" ></fb:like>

    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 210, Column 70: ID "SEARCHBOX" already defined
    …hBox"><input type="text" name="q" tabindex="1" id="searchbox" value="" /></div>

    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 210, Column 14: ID "SEARCHBOX" first defined here
    				<div id="searchBox"><input type="text" name="q" tabindex="1" id="searchbox"…
  • Warning Line 210, Column 90: NET-enabling start-tag requires SHORTTAG YES
    …hBox"><input type="text" name="q" tabindex="1" id="searchbox" value="" /></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 212, Column 81: NET-enabling start-tag requires SHORTTAG YES
    …id="searchButon"><input type="submit" value="Search" id="searchButton" /></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 226, Column 57: NET-enabling start-tag requires SHORTTAG YES
    Copyright &copy; 2004-2013 Publishers Clearing House<br /><br />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 226, Column 63: NET-enabling start-tag requires SHORTTAG YES
    Copyright &copy; 2004-2013 Publishers Clearing House<br /><br />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 227, Column 105: NET-enabling start-tag requires SHORTTAG YES
    …e the property of their respective<br />owners. Said owners do not endorse nor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 259, Column 72: cannot generate system identifier for general entity "qkwid1"
    …ospace.com/pch_meta_v3/widgets?wid=pt&qkwid1=searchbox&submitid1=searchButton"…

    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 259, Column 72: general entity "qkwid1" not defined and no default entity
    …ospace.com/pch_meta_v3/widgets?wid=pt&qkwid1=searchbox&submitid1=searchButton"…

    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.

  • Error Line 259, Column 78: reference to entity "qkwid1" for which no system identifier could be generated
    ….com/pch_meta_v3/widgets?wid=pt&qkwid1=searchbox&submitid1=searchButton"> </sc…

    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 259, Column 71: entity was defined here
    …fospace.com/pch_meta_v3/widgets?wid=pt&qkwid1=searchbox&submitid1=searchButton…
  • Warning Line 259, Column 89: cannot generate system identifier for general entity "submitid1"
    …/pch_meta_v3/widgets?wid=pt&qkwid1=searchbox&submitid1=searchButton"> </script>

    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 259, Column 89: general entity "submitid1" not defined and no default entity
    …/pch_meta_v3/widgets?wid=pt&qkwid1=searchbox&submitid1=searchButton"> </script>

    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.

  • Error Line 259, Column 98: reference to entity "submitid1" for which no system identifier could be generated
    …/pch_meta_v3/widgets?wid=pt&qkwid1=searchbox&submitid1=searchButton"> </script>

    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 259, Column 88: entity was defined here
    …/pch_meta_v3/widgets?wid=pt&qkwid1=searchbox&submitid1=searchButton"> </script>
  • Error Line 259, Column 112: required attribute "TYPE" not specified
    …/pch_meta_v3/widgets?wid=pt&qkwid1=searchbox&submitid1=searchButton"> </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 262, 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 297, 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 307, 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
  • 5.950 visits