Current news for Knoxville, TN and its surrounding communities brought to you by GoVolsXtra. Features local Knoxville, Tennessee news including sports, business, entertainment, lifestyle and more. ...

govolsxtra.com
  • Domain Name
    govolsxtra.com
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #46084
  • Page Size
    124.6 KB
  • Ip Address
    164.109.40.120
  • Heading
    H1: 0, H2: 1, H3: 22, H4: 30, H5: 9, H6: 0
  • Images
    2 GIF, 38 JPG, 3 PNG

Website Meta Analysis

  • Title
    GoVolsXtra.com: University of Tennessee sports news from The Knoxville News Sentinel
  • Meta Keyword
  • Meta Description
    Current news for Knoxville, TN and its surrounding communities brought to you by GoVolsXtra. Features local Knoxville, Tennessee news including sports, business, entertainment, lifestyle and more.

Technical Analysis

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

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

HTML Analysis

  • date: Wed, 04 Sep 2013 15:09:36 GMT
  • server: Apache/2.2.3 (Red Hat)
  • vary: Cookie,Accept-Encoding
  • content-type: text/html; charset=utf-8
  • x-varnish: 914611480 914611117
  • age: 13
  • via: 1.1 varnish
  • x-cache: HIT
  • x-cacheserver: vmp11
  • content-encoding: gzip
  • content-length: 26401
  • connection: close
  • x-google-cache-control: remote-fetch
Registrant:
Host Master
The E. W. Scripps Company
312 Walnut Street
Cincinnati OH 45202
US
email +1.8772993927 Fax:

Domain Name: govolsxtra.com

Registrar Name: Markmonitor.com
Registrar Whois: whois.markmonitor.com
Registrar Homepage: http://www.markmonitor.com

Administrative Contact:
Host Master
The E. W. Scripps Company
312 Walnut Street
Cincinnati OH 45202
US
email +1.8772993927 Fax:
Technical Contact, Zone Contact:
Host Master
The E. W. Scripps Company
312 Walnut Street
Cincinnati OH 45202
US
email +1.8772993927 Fax:

Created on..............: 2004-05-20.
Expires on..............: 2013-05-20.
Record last updated on..: 2012-04-18.

Domain servers in listed order:

ns2.scrippsing.com
ns1.scrippsing.com

DNS Analysis


DNS servers
ns1.scrippsing.com [164.109.40.124]
ns2.scrippsing.com [164.109.40.123]


DNS Records

Answer records
govolsxtra.com MX
preference: 10
exchange: inetmail.scripps.com
3600s
govolsxtra.com A 164.109.40.120 3600s
govolsxtra.com SOA
server: ns1.scrippsing.com
email: hostmaster@scrippsing.com
serial: 2013020601
refresh: 7200
retry: 3600
expire: 604800
minimum ttl: 3600
3600s
govolsxtra.com NS  ns2.scrippsing.com 3600s
govolsxtra.com NS  ns1.scrippsing.com 3600s
govolsxtra.com TXT google-site-verification=4fR79n0dKZ9YoVqp-mNoXAQzc6cZSI2Im2Jmynujv8I 3600s
govolsxtra.com TXT v=spf1 include:spf.scripps.com ip4:164.109.40.123 ip4:164.109.40.124 include:eblastengine.com ~all 3600s

Authority records

Additional records

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 74 Errors
  • 14 Warnings
Ratio Text/Html
  • 0.6387077048512027
Message Error
  • Error Line 108, Column 137: end tag for "link" omitted, but OMITTAG NO was specified
    …corp_assets/asphalt/css/jquery.smartbanner.css" type="text/css" media="screen">

    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 108, Column 1: start tag was here
    <link rel="stylesheet" href="http://media.govolsxtra.com/corp_assets/asphalt/cs…
  • Error Line 112, Column 75: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="google-play-app" content="app-id=com.scripps.knoxnews.mobile">

    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 112, Column 1: start tag was here
    <meta name="google-play-app" content="app-id=com.scripps.knoxnews.mobile">
  • Error Line 236, Column 17: there is no attribute "property"
    	<meta property="fb:app_id" content="338530941164" />

    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 335, Column 68: required attribute "type" not specified
    	<div class="adtag" id="SUPERSTITIAL"><script language="JavaScript">

    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 337, Column 29: an attribute specification must start with a name or name token
            document.write('<scr' + 'ipt language="JavaScript" src="' + 'http://ad.…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 337, Column 29: element "scr" undefined
            document.write('<scr' + 'ipt language="JavaScript" src="' + 'http://ad.…

    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 337, Column 225: delimiter "'" invalid: only S separators and TAGC allowed here
    …ve' + _demo_params + _tile_params + '" type="text/javascript"></scr' + 'ipt>');
  • Error Line 346, Column 64: required attribute "type" not specified
    			<div class="adtag" id="PENCIL"><script language="JavaScript">

    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 348, Column 29: an attribute specification must start with a name or name token
            document.write('<scr' + 'ipt language="JavaScript" src="' + 'http://ad.…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 348, Column 29: element "scr" undefined
            document.write('<scr' + 'ipt language="JavaScript" src="' + 'http://ad.…

    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 348, Column 214: delimiter "'" invalid: only S separators and TAGC allowed here
    …ve' + _demo_params + _tile_params + '" type="text/javascript"></scr' + 'ipt>');
  • Error Line 385, Column 122: there is no attribute "def"
    …"username" size="17" value="" maxlength="75" def="" type="text" tabindex="1" />

    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 386, Column 204: there is no attribute "border"
    …gin_btn.gif" title="Login" alt="Login" class="global_login_button" border="0"/>

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

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

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

  • Warning Line 405, Column 228: cannot generate system identifier for general entity "token_url"
    …t_start?ext_perm=publish_stream,email&token_url=http%3A%2F%2Fwww.govolsxtra.co…

    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 405, Column 228: general entity "token_url" not defined and no default entity
    …t_start?ext_perm=publish_stream,email&token_url=http%3A%2F%2Fwww.govolsxtra.co…

    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 405, Column 237: reference not terminated by REFC delimiter
    …xt_perm=publish_stream,email&token_url=http%3A%2F%2Fwww.govolsxtra.com%2Faccou…

    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 405, Column 237: reference to external entity in attribute value
    …xt_perm=publish_stream,email&token_url=http%3A%2F%2Fwww.govolsxtra.com%2Faccou…

    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 405, Column 237: reference to entity "token_url" for which no system identifier could be generated
    …xt_perm=publish_stream,email&token_url=http%3A%2F%2Fwww.govolsxtra.com%2Faccou…

    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 405, Column 227: entity was defined here
    …ct_start?ext_perm=publish_stream,email&token_url=http%3A%2F%2Fwww.govolsxtra.c…
  • Error Line 405, Column 465: required attribute "alt" not specified
    …ovolsxtra.com/corp_assets/asphalt/img/icons/facebook/facebook_sm_blk.jpg"/></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>.

  • Warning Line 407, Column 253: reference not terminated by REFC delimiter
    …ww.google.com/accounts/o8/id&token_url=http%3A%2F%2Fwww.govolsxtra.com%2Faccou…

    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 407, Column 253: reference to external entity in attribute value
    …ww.google.com/accounts/o8/id&token_url=http%3A%2F%2Fwww.govolsxtra.com%2Faccou…

    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 407, Column 253: reference to entity "token_url" for which no system identifier could be generated
    …ww.google.com/accounts/o8/id&token_url=http%3A%2F%2Fwww.govolsxtra.com%2Faccou…

    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 405, Column 227: entity was defined here
    …ct_start?ext_perm=publish_stream,email&token_url=http%3A%2F%2Fwww.govolsxtra.c…
  • Error Line 407, Column 477: required attribute "alt" not specified
    …ia.govolsxtra.com/corp_assets/asphalt/img/icons/google/google_sm_blk.jpg"/></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>.

  • Warning Line 409, Column 236: reference not terminated by REFC delimiter
    …fier=https%3A//me.yahoo.com/&token_url=http%3A%2F%2Fwww.govolsxtra.com%2Faccou…

    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 409, Column 236: reference to external entity in attribute value
    …fier=https%3A//me.yahoo.com/&token_url=http%3A%2F%2Fwww.govolsxtra.com%2Faccou…

    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 409, Column 236: reference to entity "token_url" for which no system identifier could be generated
    …fier=https%3A//me.yahoo.com/&token_url=http%3A%2F%2Fwww.govolsxtra.com%2Faccou…

    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 405, Column 227: entity was defined here
    …ct_start?ext_perm=publish_stream,email&token_url=http%3A%2F%2Fwww.govolsxtra.c…
  • Error Line 409, Column 458: required attribute "alt" not specified
    …edia.govolsxtra.com/corp_assets/asphalt/img/icons/yahoo/yahoo_sm_blk.jpg"/></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 411, Column 423: required attribute "alt" not specified
    ….govolsxtra.com/corp_assets/asphalt/img/icons/twitter/twitter_sm_blk.jpg"/></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 414, Column 102: there is no attribute "alt"
    …te_login" id="global_login_close" alt="Close"><img src="http://media.govolsxtr…

    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 414, Column 205: required attribute "alt" not specified
    …xtra.com/corp_assets/asphalt/img/buttons/global_login_close.png" /> </a></span>

    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 545, Column 11: ID "nav_baseball" already defined
    		<li id="nav_baseball"><a href="/news/baseball/" title="Baseball">Baseball</a>

    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 539, Column 11: ID "nav_baseball" first defined here
    		<li id="nav_baseball"><a href="http://www.govols247.com/" title="http://www.g…
  • Error Line 547, Column 8: end tag for "ul" which is not finished
    			</ul>

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

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

  • Error Line 673, Column 7: end tag for "ul" which is not finished
    		</ul>

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

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

  • Error Line 681, Column 32: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    				<div class="panel_headline">

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

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

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

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

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

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

    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 772, Column 70: required attribute "type" not specified
    							<div class="adtag" id="BIGBOX_1"><script language="JavaScript">

    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 774, Column 29: an attribute specification must start with a name or name token
            document.write('<scr' + 'ipt language="JavaScript" src="' + 'http://ad.…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 774, Column 29: element "scr" undefined
            document.write('<scr' + 'ipt language="JavaScript" src="' + 'http://ad.…

    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 774, Column 215: delimiter "'" invalid: only S separators and TAGC allowed here
    …ve' + _demo_params + _tile_params + '" type="text/javascript"></scr' + 'ipt>');
  • Error Line 857, Column 61: required attribute "type" not specified
    								<script src="http://widgets.twimg.com/j/2/widget.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 858, 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 924, Column 41: end tag for "ul" which is not finished
    				<ul class="carousel_pagination"></ul>

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

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

  • Error Line 936, Column 54: end tag for "a" omitted, but OMITTAG NO was specified
    <h4><a href="http://www.govols247.com/">Govols247</h4>

    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 936, Column 5: start tag was here
    <h4><a href="http://www.govols247.com/">Govols247</h4>
  • Error Line 937, Column 68: end tag for element "a" which is not open
    <p>The 30-day free trial is back! Time to join the conversation.</a><p>

    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 937, Column 71: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>The 30-day free trial is back! Time to join the conversation.</a><p>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 940, Column 11: end tag for "p" omitted, but OMITTAG NO was specified
    					</div> <!-- end .skybox -->

    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 937, Column 69: start tag was here
    <p>The 30-day free trial is back! Time to join the conversation.</a><p>
  • Error Line 940, Column 11: end tag for "p" omitted, but OMITTAG NO was specified
    					</div> <!-- end .skybox -->

    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 937, Column 1: start tag was here
    <p>The 30-day free trial is back! Time to join the conversation.</a><p>
  • Error Line 943, Column 27: invalid comment declaration: found name character outside comment but inside comment declaration
    						<!-- GVX Facebook --->
  • Info Line 943, Column 7: comment declaration started here
    						<!-- GVX Facebook --->
  • Error Line 979, Column 110: end tag for "a" omitted, but OMITTAG NO was specified
    …e.com/us/app/knoxnews/id369943355?mt=8" title="Knoxnews iPhone">iPhone App</h4>

    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 979, Column 5: start tag was here
    <h4><a href="http://itunes.apple.com/us/app/knoxnews/id369943355?mt=8" title="K…
  • Error Line 980, Column 62: end tag for element "a" which is not open
    <p>There's a free knoxnews iPhone app in the iTunes store.</a></p>

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

    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 1455, Column 45: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            <a href="/videos/"><div class="prev"></div></a>

    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 1457, Column 45: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            <a href="/videos/"><div class="next">   </div></a>

    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 1698, Column 76: required attribute "type" not specified
    					<div class="adtag" id="LEADERBOARD_HOME"><script language="JavaScript">

    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 1700, Column 29: an attribute specification must start with a name or name token
            document.write('<scr' + 'ipt language="JavaScript" src="' + 'http://ad.…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 1700, Column 29: element "scr" undefined
            document.write('<scr' + 'ipt language="JavaScript" src="' + 'http://ad.…

    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 1700, Column 214: delimiter "'" invalid: only S separators and TAGC allowed here
    …ow' + _demo_params + _tile_params + '" type="text/javascript"></scr' + 'ipt>');
  • Error Line 2348, Column 189: required attribute "alt" not specified
    …540647af67.r35.cf1.rackcdn.com/17607000-4b4f-4eef-8cf8-b707eb9d1cc3.jpg" /></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 2357, Column 189: required attribute "alt" not specified
    …540647af67.r35.cf1.rackcdn.com/349d7692-8611-4144-836f-a01b85752f28.jpg" /></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 2366, Column 189: required attribute "alt" not specified
    …540647af67.r35.cf1.rackcdn.com/7529ad62-1ac3-431e-b5f4-b49ce22249bd.jpg" /></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 2375, Column 189: required attribute "alt" not specified
    …540647af67.r35.cf1.rackcdn.com/09dcc3ba-e6bf-4c0a-8cb4-93e79625088f.jpg" /></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 2384, Column 189: required attribute "alt" not specified
    …540647af67.r35.cf1.rackcdn.com/bea52fe6-5587-4c00-af43-8b1501911309.jpg" /></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 2393, Column 189: required attribute "alt" not specified
    …540647af67.r35.cf1.rackcdn.com/989c2883-3a84-44d3-8aec-824d2153c0b7.jpg" /></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 2413, Column 189: required attribute "alt" not specified
    …540647af67.r35.cf1.rackcdn.com/17607000-4b4f-4eef-8cf8-b707eb9d1cc3.jpg" /></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 2422, Column 189: required attribute "alt" not specified
    …540647af67.r35.cf1.rackcdn.com/349d7692-8611-4144-836f-a01b85752f28.jpg" /></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 2431, Column 189: required attribute "alt" not specified
    …540647af67.r35.cf1.rackcdn.com/7529ad62-1ac3-431e-b5f4-b49ce22249bd.jpg" /></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 2440, Column 189: required attribute "alt" not specified
    …540647af67.r35.cf1.rackcdn.com/09dcc3ba-e6bf-4c0a-8cb4-93e79625088f.jpg" /></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 2449, Column 189: required attribute "alt" not specified
    …540647af67.r35.cf1.rackcdn.com/bea52fe6-5587-4c00-af43-8b1501911309.jpg" /></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 2458, Column 189: required attribute "alt" not specified
    …540647af67.r35.cf1.rackcdn.com/989c2883-3a84-44d3-8aec-824d2153c0b7.jpg" /></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 2481, Column 68: required attribute "type" not specified
    					<div class="adtag" id="BIGBOX_2"><script language="JavaScript">

    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 2483, Column 29: an attribute specification must start with a name or name token
            document.write('<scr' + 'ipt language="JavaScript" src="' + 'http://ad.…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 2483, Column 29: element "scr" undefined
            document.write('<scr' + 'ipt language="JavaScript" src="' + 'http://ad.…

    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 2483, Column 215: delimiter "'" invalid: only S separators and TAGC allowed here
    …ow' + _demo_params + _tile_params + '" type="text/javascript"></scr' + 'ipt>');
  • Error Line 2537, Column 11: 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 2537, Column 11: document type does not allow element "style" here
    				<style>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 2549, Column 60: cannot generate system identifier for general entity "process"
    …pictopia.com/perl/gal?provider_id=203&process=deliver&page=requests_xsl" title…

    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 2549, Column 60: general entity "process" not defined and no default entity
    …pictopia.com/perl/gal?provider_id=203&process=deliver&page=requests_xsl" title…

    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 2549, Column 67: reference not terminated by REFC delimiter
    …a.com/perl/gal?provider_id=203&process=deliver&page=requests_xsl" title="Photo…

    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 2549, Column 67: reference to external entity in attribute value
    …a.com/perl/gal?provider_id=203&process=deliver&page=requests_xsl" title="Photo…

    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 2549, Column 67: reference to entity "process" for which no system identifier could be generated
    …a.com/perl/gal?provider_id=203&process=deliver&page=requests_xsl" title="Photo…

    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 2549, Column 59: entity was defined here
    …/pictopia.com/perl/gal?provider_id=203&process=deliver&page=requests_xsl" titl…
  • Warning Line 2549, Column 76: cannot generate system identifier for general entity "page"
    …l/gal?provider_id=203&process=deliver&page=requests_xsl" title="Photo reprints…

    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 2549, Column 76: general entity "page" not defined and no default entity
    …l/gal?provider_id=203&process=deliver&page=requests_xsl" title="Photo reprints…

    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 2549, Column 80: reference not terminated by REFC delimiter
    …l?provider_id=203&process=deliver&page=requests_xsl" title="Photo reprints">Ph…

    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 2549, Column 80: reference to external entity in attribute value
    …l?provider_id=203&process=deliver&page=requests_xsl" title="Photo reprints">Ph…

    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 2549, Column 80: reference to entity "page" for which no system identifier could be generated
    …l?provider_id=203&process=deliver&page=requests_xsl" title="Photo reprints">Ph…

    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 2549, Column 75: entity was defined here
    …rl/gal?provider_id=203&process=deliver&page=requests_xsl" title="Photo reprint…
  • Error Line 2632, Column 10: 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 2697, Column 80: required attribute "alt" not specified
    …#deals_image").append("<img src='" + deal_image + "' style='width:292px;' />");

    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 2697, Column 80: document type does not allow element "img" here
    …#deals_image").append("<img src='" + deal_image + "' style='width:292px;' />");

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Visitor Analysis

Daily Visitor
  • 2.800 visits