Skip to main content Google Bing Yahoo Site Menu Home Residential Business Help Desk Contact Industry leader. See why we're your Recommended Source of Fiber Access Your Email Anywhere at Anytime Whether on ...

ptd.net
  • Domain Name
    ptd.net
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #59835
  • Page Size
    26.9 KB
  • Ip Address
    209.50.150.195
  • Heading
    H1: 4, H2: 4, H3: 6, H4: 0, H5: 0, H6: 0
  • Images
    9 GIF, 4 JPG, 2 PNG

Website Meta Analysis

  • Title
    PTD
  • Meta Keyword
  • Meta Description
    Skip to main content Google Bing Yahoo Site Menu Home Residential Business Help Desk Contact Industry leader. See why we're your Recommended Source of Fiber Access Your Email Anywhere at Anytime Whether on vacation or at home, you can access ...

Technical Analysis

  • Webserver
    Apache/2.2.27 (CentOS)
  • Ip Address
    209.50.150.195
  • Domain Age
    19 Years, 2 Months, 12 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from ptd.net.

HTML Analysis

  • date: Wed, 08 Oct 2014 01:12:07 GMT
  • server: Apache/2.2.27 (CentOS)
  • x-powered-by: PHP/5.5.17
  • x-drupal-cache: HIT
  • etag: "1412730015.233-1"
  • content-language: en
  • x-generator: Drupal 7 (http://drupal.org)
  • cache-control: public, max-age=1800
  • last-modified: Wed, 08 Oct 2014 01:00:15 +0000
  • expires: Sun, 19 Nov 1978 05:00:00 GMT
  • vary: Cookie,Accept-Encoding
  • content-encoding: gzip
  • content-length: 6764
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
PenTeleData Inc
471 Delaware Ave
Palmerton, Pa 18071
US

Domain name: PTD.NET

Administrative Contact:
Administrator, Systems email
471 Delaware Ave
Palmerton, Pa 18071
US
610-826-9152
Technical Contact:
Admininstration, System email
540 Delaware Ave
Palmerton, Pa 18071
US
1-800-281-3564 Fax: (610)826-4707


Record last updated on 20-Sep-2011.
Record expires on 03-Aug-2013.
Record created on 04-Aug-1994.


Domain servers in listed order:
DNS5.PTD.NET 204.186.80.169
DNS6.PTD.NET 204.186.80.249
DNS4.PTD.NET 207.44.0.1
DNS3.PTD.NET 204.186.0.203
DNS1.PTD.NET 204.186.0.201
DNS2.PTD.NET 207.44.96.129

Domain status: ok

DNS Analysis


DNS servers
dns6.ptd.net [204.186.80.249]
dns3.ptd.net [204.186.0.203]
dns4.ptd.net [207.44.0.1]
dns2.ptd.net [207.44.96.129]
dns1.ptd.net [204.186.0.201]
dns5.ptd.net [204.186.80.169]


DNS Records

Answer records
ptd.net SOA
server: dns1.ptd.net
email: dns-request@corp.ptd.net
serial: 2013022201
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 10800
86400s
ptd.net TXT v=spf1 ip4:207.44.96.0/24 ip4:204.186.29.0/24 ip4:204.186.200.0/24 ip4:204.186.204.0/24 ip4:204.186.110.182 -all 86400s
ptd.net A 204.186.48.102 86400s
ptd.net A 204.186.48.107 86400s
ptd.net A 204.186.48.101 86400s
ptd.net MX
preference: 10
exchange: smtpin.ptd.net
3600s
ptd.net NS  dns2.ptd.net 86400s
ptd.net NS  dns3.ptd.net 86400s
ptd.net NS  dns4.ptd.net 86400s
ptd.net NS  dns5.ptd.net 86400s
ptd.net NS  dns6.ptd.net 86400s
ptd.net NS  dns1.ptd.net 86400s

Authority records

Additional records
smtpin.ptd.net A 207.44.97.35 600s
dns1.ptd.net A 204.186.0.201 86400s
dns2.ptd.net A 207.44.96.129 86400s
dns3.ptd.net A 204.186.0.203 86400s
dns4.ptd.net A 207.44.0.1 86400s
dns5.ptd.net A 204.186.80.169 86400s
dns6.ptd.net A 204.186.80.249 86400s

IP 209.50.150.195 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 36 Errors
  • 16 Warnings
Ratio Text/Html
  • 0.6839468525375736
Message Error
  • Error Line 11, Column 45: end tag for "meta" omitted, but OMITTAG NO was specified
    		<meta http-equiv="refresh" content="3600">

    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 11, Column 3: start tag was here
    		<meta http-equiv="refresh" content="3600">
  • Error Line 106, Column 18: there is no attribute "LANGUAGE"
    <SCRIPT LANGUAGE="JavaScript1.2" SRC="/yellow_brix/sports_middle_section/src/pr…

    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 106, Column 38: there is no attribute "SRC"
    <SCRIPT LANGUAGE="JavaScript1.2" SRC="/yellow_brix/sports_middle_section/src/pr…

    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 106, Column 91: element "SCRIPT" undefined
    …aScript1.2" SRC="/yellow_brix/sports_middle_section/src/prototype.js"></SCRIPT>

    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 107, Column 38: there is no attribute "src"
    <SCRIPT LANGUAGE="JavaScript1.2" src="/yellow_brix/stocks.js" type="text/javasc…

    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 107, Column 68: there is no attribute "type"
    …E="JavaScript1.2" src="/yellow_brix/stocks.js" type="text/javascript"></script>

    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 107, Column 85: element "SCRIPT" undefined
    …E="JavaScript1.2" src="/yellow_brix/stocks.js" type="text/javascript"></script>

    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 107, Column 94: end tag for element "script" which is not open
    …E="JavaScript1.2" src="/yellow_brix/stocks.js" type="text/javascript"></script>

    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 141, Column 39: character "<" is the first character of a delimiter but occurred as data
    		current_Minutes = ( current_Minutes < 10 ? "0" : "" ) + current_Minutes;

    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 142, Column 39: character "<" is the first character of a delimiter but occurred as data
    		current_Seconds = ( current_Seconds < 10 ? "0" : "" ) + current_Seconds;

    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 143, Column 35: character "<" is the first character of a delimiter but occurred as data
    		var timeOfDay = ( current_Hours < 12 ) ? "AM" : "PM";

    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 166, Column 8: end tag for "SCRIPT" omitted, but OMITTAG NO was specified
    	</head>

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

  • Info Line 107, Column 1: start tag was here
    <SCRIPT LANGUAGE="JavaScript1.2" src="/yellow_brix/stocks.js" type="text/javasc…
  • Error Line 186, Column 75: required attribute "alt" not specified
    	<a href="http://ptd.net"><img id="ptd_logo" src="styles/PTD/weareptd.png"></a>

    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 186, Column 79: end tag for "img" omitted, but OMITTAG NO was specified
    	<a href="http://ptd.net"><img id="ptd_logo" src="styles/PTD/weareptd.png"></a>

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

  • Info Line 186, Column 27: start tag was here
    	<a href="http://ptd.net"><img id="ptd_logo" src="styles/PTD/weareptd.png"></a>
  • Error Line 190, Column 272: value of attribute "frameborder" cannot be "no"; must be one of "1", "0"
    …right;" scrolling="no" frameborder="no" ALLOWTRANSPARENCY="true"></iframe></di…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 190, Column 292: there is no attribute "ALLOWTRANSPARENCY"
    …ight;" scrolling="no" frameborder="no" ALLOWTRANSPARENCY="true"></iframe></div>

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

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

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

  • Warning Line 239, Column 19: character "&" is the first character of a delimiter but occurred as data
    alt="" />Products & Services&nbsp;<img

    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 278, Column 20: value of attribute "valign" cannot be "center"; must be one of "top", "middle", "bottom", "baseline"
    	<td valign="center">

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 282, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td valign=bottom align=right>
  • Error Line 282, Column 25: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td valign=bottom align=right>
  • Error Line 284, Column 14: there is no attribute "name"
    <SELECT name="location" id="web_search_select">

    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 284, Column 28: there is no attribute "id"
    <SELECT name="location" id="web_search_select">

    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 284, Column 47: element "SELECT" undefined
    <SELECT name="location" id="web_search_select">

    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 285, Column 17: there is no attribute "label"
    <OPTGROUP label="Primary Search">

    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 285, Column 33: element "OPTGROUP" undefined
    <OPTGROUP label="Primary Search">

    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 286, Column 15: there is no attribute "value"
    <OPTION value="1" SELECTED>Google</OPTION>

    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 286, Column 27: "SELECTED" is not a member of a group specified for any attribute
    <OPTION value="1" SELECTED>Google</OPTION>
  • Error Line 286, Column 27: element "OPTION" undefined
    <OPTION value="1" SELECTED>Google</OPTION>

    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 287, Column 19: element "OPTION" undefined
    <OPTION value="2" >Yahoo!</OPTION>

    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 288, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <OPTION value=3>Bing</OPTION>
  • Error Line 288, Column 16: element "OPTION" undefined
    <OPTION value=3>Bing</OPTION>

    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 289, Column 18: element "OPTION" undefined
    <OPTION value="4">Ask.com</OPTION>

    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 290, Column 11: end tag for element "optgroup" which is not open
    </optgroup>

    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 291, Column 34: element "OPTGROUP" undefined
    <OPTGROUP label="Combined Search">

    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 292, Column 18: element "OPTION" undefined
    <OPTION value="5">Dog Pile</OPTION>

    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 293, Column 18: element "OPTION" undefined
    <OPTION value="8">Gigablast</OPTION>

    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 294, Column 11: end tag for element "optgroup" which is not open
    </optgroup>

    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 295, Column 31: element "OPTGROUP" undefined
    <OPTGROUP label="Other Search">

    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 296, Column 18: element "OPTION" undefined
    <OPTION value="6">About.com</OPTION>

    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 297, Column 18: element "OPTION" undefined
    <OPTION value="7">Findlaw.com</OPTION>

    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 298, Column 11: end tag for element "optgroup" which is not open
    </optgroup>

    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 299, Column 9: end tag for "OPTGROUP" omitted, but OMITTAG NO was specified
    </SELECT>

    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 295, Column 1: start tag was here
    <OPTGROUP label="Other Search">
  • Error Line 299, Column 9: end tag for "OPTGROUP" omitted, but OMITTAG NO was specified
    </SELECT>

    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 291, Column 1: start tag was here
    <OPTGROUP label="Combined Search">
  • Error Line 299, Column 9: end tag for "OPTGROUP" omitted, but OMITTAG NO was specified
    </SELECT>

    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 285, Column 1: start tag was here
    <OPTGROUP label="Primary Search">
  • Error Line 300, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <input id="web_search_string" type="text" size=24 name="search" value"" />
  • Error Line 300, Column 70: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    <input id="web_search_string" type="text" size=24 name="search" value"" />

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 300, Column 71: end tag for "input" omitted, but OMITTAG NO was specified
    <input id="web_search_string" type="text" size=24 name="search" value"" />

    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 300, Column 1: start tag was here
    <input id="web_search_string" type="text" size=24 name="search" value"" />
  • Error Line 301, Column 43: value of attribute "type" cannot be "Submit"; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    <input id="web_search_submit" type="Submit" value="GO!" name="Search the Web" />

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 374, Column 328: there is no attribute "src"
    …ode" value="transparent" /><embed src="styles/PTD/ptd-flash.swf" quality="high…

    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 374, Column 363: there is no attribute "quality"
    …rc="styles/PTD/ptd-flash.swf" quality="high" pluginspage="http://www.macromedi…

    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 374, Column 382: there is no attribute "pluginspage"
    …flash.swf" quality="high" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 374, Column 433: there is no attribute "type"
    …acromedia.com/go/getflashplayer" type="application/x-shockwave-flash" width="7…

    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 374, Column 471: there is no attribute "width"
    …"application/x-shockwave-flash" width="713" height="170" wmode="transparent"><…

    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 374, Column 484: there is no attribute "height"
    …x-shockwave-flash" width="713" height="170" wmode="transparent"></embed></obje…

    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 374, Column 496: there is no attribute "wmode"
    …ave-flash" width="713" height="170" wmode="transparent"></embed></object><br />

    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 374, Column 509: element "embed" undefined
    …ave-flash" width="713" height="170" wmode="transparent"></embed></object><br />

    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 387, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><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 387, Column 1: start tag was here
    <br><br />
  • Error Line 388, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><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 388, Column 1: start tag was here
    <br><br />
  • Error Line 417, Column 48: end tag for "br" omitted, but OMITTAG NO was specified
    						<span class="moduletitle">PenTeleData<br>Customer Tools</span>

    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 417, Column 44: start tag was here
    						<span class="moduletitle">PenTeleData<br>Customer Tools</span>
  • Error Line 422, Column 94: there is no attribute "border"
    …44" height="42" scrolling="no" border="0" marginwidth="0" style="border:none;"…

    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 423, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    </iframe><br><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 423, Column 10: start tag was here
    </iframe><br><br>
  • Error Line 423, Column 18: end tag for "br" omitted, but OMITTAG NO was specified
    </iframe><br><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 423, Column 14: start tag was here
    </iframe><br><br>
  • Error Line 435, 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 435, Column 1: start tag was here
    <br>
  • Error Line 437, Column 63: required attribute "alt" not specified
    <img src="styles/PTD/ptd_webmail.jpg" style="margin-top:-8px;">

    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 437, Column 64: end tag for "img" omitted, but OMITTAG NO was specified
    <img src="styles/PTD/ptd_webmail.jpg" style="margin-top:-8px;">

    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 437, Column 1: start tag was here
    <img src="styles/PTD/ptd_webmail.jpg" style="margin-top:-8px;">
  • Error Line 443, Column 36: required attribute "alt" not specified
    	<img src="/show_image.php?id=1083">

    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 443, Column 37: end tag for "img" omitted, but OMITTAG NO was specified
    	<img src="/show_image.php?id=1083">

    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 443, Column 2: start tag was here
    	<img src="/show_image.php?id=1083">
  • Error Line 450, Column 111: required attribute "alt" not specified
    …ter.com/#!/PenTeleData" class="c_tools"><img src="/show_image.php?id=1084"></a>

    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 450, Column 115: end tag for "img" omitted, but OMITTAG NO was specified
    …ter.com/#!/PenTeleData" class="c_tools"><img src="/show_image.php?id=1084"></a>

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

  • Info Line 450, Column 77: start tag was here
    …ter.com/#!/PenTeleData" class="c_tools"><img src="/show_image.php?id=1084"></a>
  • Error Line 465, Column 49: end tag for "hr" omitted, but OMITTAG NO was specified
    </div><hr class="module_divider" align="center">

    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 465, Column 7: start tag was here
    </div><hr class="module_divider" align="center">
  • Error Line 471, Column 41: end tag for "br" omitted, but OMITTAG NO was specified
    						<span class="moduletitle">Mozy<br>Online Backup</span>

    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 471, Column 37: start tag was here
    						<span class="moduletitle">Mozy<br>Online Backup</span>
  • Warning Line 476, Column 52: cannot generate system identifier for general entity "kbid"
    …ef="http://www.mozy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" s…

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

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

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

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

  • Error Line 476, Column 52: general entity "kbid" not defined and no default entity
    …ef="http://www.mozy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" s…

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

  • Warning Line 476, Column 56: reference not terminated by REFC delimiter
    …http://www.mozy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="…

    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 476, Column 56: reference to external entity in attribute value
    …http://www.mozy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="…

    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 476, Column 56: reference to entity "kbid" for which no system identifier could be generated
    …http://www.mozy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="…

    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 476, Column 51: entity was defined here
    …ref="http://www.mozy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" …
  • Warning Line 476, Column 64: cannot generate system identifier for general entity "m"
    …ww.mozy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="http://a…

    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 476, Column 64: general entity "m" not defined and no default entity
    …ww.mozy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="http://a…

    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 476, Column 65: reference not terminated by REFC delimiter
    …w.mozy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="http://af…

    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 476, Column 65: reference to external entity in attribute value
    …w.mozy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="http://af…

    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 476, Column 65: reference to entity "m" for which no system identifier could be generated
    …w.mozy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="http://af…

    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 476, Column 63: entity was defined here
    …www.mozy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="http://…
  • Warning Line 476, Column 69: cannot generate system identifier for general entity "i"
    …zy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="http://affili…

    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 476, Column 69: general entity "i" not defined and no default entity
    …zy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="http://affili…

    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 476, Column 70: reference not terminated by REFC delimiter
    …y.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="http://affilia…

    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 476, Column 70: reference to external entity in attribute value
    …y.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="http://affilia…

    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 476, Column 70: reference to entity "i" for which no system identifier could be generated
    …y.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="http://affilia…

    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 476, Column 68: entity was defined here
    …ozy.com/?ref=3f9a896b&kbid=126312&m=22&i=92"><img border="0" src="http://affil…
  • Warning Line 476, Column 140: cannot generate system identifier for general entity "mm"
    …/affiliates.mozy.com/b.aspx?id=126312&mm=22&img=home-insurance-200x200.gif"/><…

    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 476, Column 140: general entity "mm" not defined and no default entity
    …/affiliates.mozy.com/b.aspx?id=126312&mm=22&img=home-insurance-200x200.gif"/><…

    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 476, Column 142: reference not terminated by REFC delimiter
    …ffiliates.mozy.com/b.aspx?id=126312&mm=22&img=home-insurance-200x200.gif"/></a…

    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 476, Column 142: reference to external entity in attribute value
    …ffiliates.mozy.com/b.aspx?id=126312&mm=22&img=home-insurance-200x200.gif"/></a…

    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 476, Column 142: reference to entity "mm" for which no system identifier could be generated
    …ffiliates.mozy.com/b.aspx?id=126312&mm=22&img=home-insurance-200x200.gif"/></a…

    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 476, Column 139: entity was defined here
    …//affiliates.mozy.com/b.aspx?id=126312&mm=22&img=home-insurance-200x200.gif"/>…
  • Warning Line 476, Column 146: cannot generate system identifier for general entity "img"
    …iates.mozy.com/b.aspx?id=126312&mm=22&img=home-insurance-200x200.gif"/></a></c…

    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 476, Column 146: general entity "img" not defined and no default entity
    …iates.mozy.com/b.aspx?id=126312&mm=22&img=home-insurance-200x200.gif"/></a></c…

    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 476, Column 149: reference not terminated by REFC delimiter
    …es.mozy.com/b.aspx?id=126312&mm=22&img=home-insurance-200x200.gif"/></a></cent…

    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 476, Column 149: reference to external entity in attribute value
    …es.mozy.com/b.aspx?id=126312&mm=22&img=home-insurance-200x200.gif"/></a></cent…

    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 476, Column 149: reference to entity "img" for which no system identifier could be generated
    …es.mozy.com/b.aspx?id=126312&mm=22&img=home-insurance-200x200.gif"/></a></cent…

    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 476, Column 145: entity was defined here
    …liates.mozy.com/b.aspx?id=126312&mm=22&img=home-insurance-200x200.gif"/></a></…
  • Error Line 476, Column 178: required attribute "alt" not specified
    ….mozy.com/b.aspx?id=126312&mm=22&img=home-insurance-200x200.gif"/></a></center>

    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 485, Column 49: end tag for "hr" omitted, but OMITTAG NO was specified
    </div><hr class="module_divider" align="center">

    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 485, Column 7: start tag was here
    </div><hr class="module_divider" align="center">
  • Error Line 491, Column 48: end tag for "br" omitted, but OMITTAG NO was specified
    						<span class="moduletitle">PenTeleData<br>Community Ads</span>

    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 491, Column 44: start tag was here
    						<span class="moduletitle">PenTeleData<br>Community Ads</span>
  • Error Line 505, Column 49: end tag for "hr" omitted, but OMITTAG NO was specified
    </div><hr class="module_divider" align="center">

    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 505, Column 7: start tag was here
    </div><hr class="module_divider" align="center">
  • Error Line 511, Column 50: end tag for "br" omitted, but OMITTAG NO was specified
    						<span class="moduletitle">Entertainment<br>and Fun Features</span>

    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 511, Column 46: start tag was here
    						<span class="moduletitle">Entertainment<br>and Fun Features</span>
  • Error Line 527, Column 49: end tag for "hr" omitted, but OMITTAG NO was specified
    </div><hr class="module_divider" align="center">

    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 527, Column 7: start tag was here
    </div><hr class="module_divider" align="center">
  • Error Line 533, Column 49: end tag for "br" omitted, but OMITTAG NO was specified
    						<span class="moduletitle">Pennsylvania<br>Lottery Spot</span>

    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 533, Column 45: start tag was here
    						<span class="moduletitle">Pennsylvania<br>Lottery Spot</span>
  • Error Line 547, Column 49: end tag for "hr" omitted, but OMITTAG NO was specified
    </div><hr class="module_divider" align="center">

    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 547, Column 7: start tag was here
    </div><hr class="module_divider" align="center">
  • Error Line 563, 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 563, Column 1: start tag was here
    <br>
  • Warning Line 858, Column 19: character "&" is the first character of a delimiter but occurred as data
    alt="" />Articles & Awards&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 868, Column 23: character "&" is the first character of a delimiter but occurred as data
    alt="" />Sponsorships & Charities&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.

Visitor Analysis

Daily Visitor
  • 3.033 visits