Watch Live Cricket Matches Online. Watch Live Cricket Streaming on Internet. Watch Free Live Cricket on your PC ...

cricket-tv.net
  • Domain Name
    cricket-tv.net
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #285595
  • Page Size
    12.2 KB
  • Ip Address
    141.101.117.209
  • Heading
    H1: 0, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 10 JPG, 6 PNG

Website Meta Analysis

  • Title
    Live Cricket - Watch Cricket Live Streaming, Watch Live Cricket Online Free
  • Meta Keyword
    live cricket, watch live cricket, live cricket match, free cricket Tv, live cricket Online, live cricket Channel online, Cricket-TV, Free Online Cricket
  • Meta Description
    Watch Live Cricket Matches Online. Watch Live Cricket Streaming on Internet. Watch Free Live Cricket on your PC

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    141.101.117.209
  • Domain Age
    8 Months, 20 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from cricket-tv.net.

HTML Analysis

  • server: cloudflare-nginx
  • date: Sat, 20 Jul 2013 13:10:04 GMT
  • content-type: text/html
  • connection: keep-alive
  • last-modified: Thu, 11 Jul 2013 06:16:12 GMT
  • cf-ray: 90fe3b5576c05bb
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
NOTICE AND TERMS OF USE: You are not authorized to access or query our WHOIS
database through the use of high-volume, automated, electronic processes. The
Data in our WHOIS database is provided for information purposes only, and to
assist persons in obtaining information about or related to a domain name
registration record. We do not guarantee its accuracy. By submitting a WHOIS
query, you agree to abide by the following terms of use: You agree that you may
use this Data only for lawful purposes and that under no circumstances will you
use this Data to: (1) allow, enable, or otherwise support the transmission of
mass unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes that
apply to us (or our computer systems). The compilation, repackaging,
dissemination or other use of this Data is expressly prohibited without our
prior written consent. We reserve the right to terminate your access to the
WHOIS database at our sole discretion, including without limitation, for
excessive querying of the WHOIS database or for failure to otherwise abide by
this policy. We reserve the right to modify these terms at any time.

Domains - cheap, easy, and secure at NameSilo.com

http://www.namesilo.com


Domain Name: cricket-tv.net
Created On: 2012-11-02
Expiration Date: 2013-11-02
Name Server: NS1.ALTUSHOST.COM
Name Server: NS2.ALTUSHOST.COM
Registrant Name: Mail Rejected See PrivacyGuardian.org
Registrant Organization: PrivacyGuardian.org
Registrant Street1: 1928 E. Highland Ave. Ste F104
Registrant Street2: PMB# 255
Registrant Street3: NOTE - All Postal Mails Rejected - visit PrivacyGuardian.org
Registrant City: Phoenix
Registrant State/Province: Arizona
Registrant Postal Code: 85016
Registrant Country: US
Registrant Phone: 347-871-7726
Registrant Fax:
Registrant Email: email
Admin Name: Mail Rejected See PrivacyGuardian.org
Admin Organization: PrivacyGuardian.org
Admin Street1: 1928 E. Highland Ave. Ste F104
Admin Street2: PMB# 255
Admin Street3: NOTE - All Postal Mails Rejected - visit PrivacyGuardian.org
Admin City: Phoenix
Admin State/Province: Arizona
Admin Postal Code: 85016
Admin Country: US
Admin Phone: 347-871-7726
Admin Fax:
Admin Email: email
Billing Name: Mail Rejected See PrivacyGuardian.org
Billing Organization: PrivacyGuardian.org
Billing Street1: 1928 E. Highland Ave. Ste F104
Billing Street2: PMB# 255
Billing Street3: NOTE - All Postal Mails Rejected - visit PrivacyGuardian.org
Billing City: Phoenix
Billing State/Province: Arizona
Billing Postal Code: 85016
Billing Country: US
Billing Phone: 347-871-7726
Billing Fax:
Billing Email: email
Tech Name: Mail Rejected See PrivacyGuardian.org
Tech Organization: PrivacyGuardian.org
Tech Street1: 1928 E. Highland Ave. Ste F104
Tech Street2: PMB# 255
Tech Street3: NOTE - All Postal Mails Rejected - visit PrivacyGuardian.org
Tech City: Phoenix
Tech State/Province: Arizona
Tech Postal Code: 85016
Tech Country: US
Tech Phone: 347-871-7726
Tech Fax:
Tech Email: email

Register your domain now at www.NameSilo.com - Domains. Cheap, Fast and Secure


DNS Analysis


DNS servers
ns1.altushost.com [37.46.127.165]
ns2.altushost.com [37.46.127.166]


DNS Records

Answer records
cricket-tv.net TXT v=spf1 +a +mx +ip4:37.46.127.164 ?all 14400s
cricket-tv.net MX
preference: 0
exchange: cricket-tv.net
14400s
cricket-tv.net SOA
server: ns1.altushost.com
email: techs@altushost.com
serial: 2012110202
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
cricket-tv.net NS  ns2.altushost.com 86400s
cricket-tv.net NS  ns1.altushost.com 86400s
cricket-tv.net A 37.46.127.164 14400s

Authority records

Additional records
cricket-tv.net A 37.46.127.164 14400s
ns1.altushost.com A 37.46.127.165 14400s
ns2.altushost.com A 37.46.127.166 14400s

IP 141.101.117.209 Analysis

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 94 Errors
  • 16 Warnings
Ratio Text/Html
  • 0.8271397746343803
Message Error
  • Error Line 7, Column 12: there is no attribute "NAME"
    <META NAME="DESCRIPTION" CONTENT="Watch Live Cricket Matches Online. Watch Live…

    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 7, Column 34: there is no attribute "CONTENT"
    <META NAME="DESCRIPTION" CONTENT="Watch Live Cricket Matches Online. Watch Live…

    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 7, Column 148: element "META" undefined
    …Watch Live Cricket Streaming on Internet. Watch Free Live Cricket on your PC ">

    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 8, Column 185: element "META" undefined
    … cricket Online, live cricket Channel online, Cricket-TV, Free Online Cricket">

    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 11, Column 16: there is no attribute "property"
    <meta property="og:type" content="article"/>

    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 23, Column 7: end tag for "META" 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 8, Column 1: start tag was here
    <META NAME="KEYWORDS" CONTENT="live cricket, watch live cricket, live cricket m…
  • Error Line 23, Column 7: end tag for "META" 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 7, Column 1: start tag was here
    <META NAME="DESCRIPTION" CONTENT="Watch Live Cricket Matches Online. Watch Live…
  • Error Line 35, Column 13: there is no attribute "SRC"
    <IFRAME SRC="http://ad.yieldmanager.com/st?ad_type=iframe&ad_size=468x60&sectio…

    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 35, Column 59: cannot generate system identifier for general entity "ad_size"
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=$…

    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 35, Column 59: general entity "ad_size" not defined and no default entity
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=$…

    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 35, Column 66: reference not terminated by REFC delimiter
    …dmanager.com/st?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_UR…

    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 35, Column 66: reference to external entity in attribute value
    …dmanager.com/st?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_UR…

    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 35, Column 66: reference to entity "ad_size" for which no system identifier could be generated
    …dmanager.com/st?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_UR…

    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 35, Column 58: entity was defined here
    …/ad.yieldmanager.com/st?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=…
  • Warning Line 35, Column 74: cannot generate system identifier for general entity "section"
    ….com/st?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAM…

    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 35, Column 74: general entity "section" not defined and no default entity
    ….com/st?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAM…

    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 35, Column 81: reference not terminated by REFC delimiter
    …?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER…

    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 35, Column 81: reference to external entity in attribute value
    …?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER…

    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 35, Column 81: reference to entity "section" for which no system identifier could be generated
    …?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER…

    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 35, Column 73: entity was defined here
    …r.com/st?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRA…
  • Warning Line 35, Column 90: cannot generate system identifier for general entity "pub_url"
    …iframe&ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER="0" SCRO…

    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 35, Column 90: general entity "pub_url" not defined and no default entity
    …iframe&ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER="0" SCRO…

    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 35, Column 97: reference not terminated by REFC delimiter
    …ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER="0" SCROLLING="…

    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 35, Column 97: reference to external entity in attribute value
    …ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER="0" SCROLLING="…

    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 35, Column 97: reference to entity "pub_url" for which no system identifier could be generated
    …ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER="0" SCROLLING="…

    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 35, Column 89: entity was defined here
    …=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER="0" SCR…
  • Error Line 35, Column 122: there is no attribute "FRAMEBORDER"
    …21187&pub_url=${PUB_URL}" FRAMEBORDER="0" SCROLLING="no" MARGINHEIGHT="0" MARG…

    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 35, Column 136: there is no attribute "SCROLLING"
    …${PUB_URL}" FRAMEBORDER="0" SCROLLING="no" MARGINHEIGHT="0" MARGINWIDTH="0" TO…

    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 35, Column 154: there is no attribute "MARGINHEIGHT"
    …ORDER="0" SCROLLING="no" MARGINHEIGHT="0" MARGINWIDTH="0" TOPMARGIN="0" LEFTMA…

    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 35, Column 170: there is no attribute "MARGINWIDTH"
    …ING="no" MARGINHEIGHT="0" MARGINWIDTH="0" TOPMARGIN="0" LEFTMARGIN="0" ALLOWTR…

    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 35, Column 184: there is no attribute "TOPMARGIN"
    …NHEIGHT="0" MARGINWIDTH="0" TOPMARGIN="0" LEFTMARGIN="0" ALLOWTRANSPARENCY="tr…

    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 35, Column 199: there is no attribute "LEFTMARGIN"
    …GINWIDTH="0" TOPMARGIN="0" LEFTMARGIN="0" ALLOWTRANSPARENCY="true" WIDTH="468"…

    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 35, Column 221: there is no attribute "ALLOWTRANSPARENCY"
    …N="0" LEFTMARGIN="0" ALLOWTRANSPARENCY="true" WIDTH="468" HEIGHT="60"></IFRAME>

    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 35, Column 234: there is no attribute "WIDTH"
    …N="0" LEFTMARGIN="0" ALLOWTRANSPARENCY="true" WIDTH="468" HEIGHT="60"></IFRAME>

    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 35, Column 247: there is no attribute "HEIGHT"
    …N="0" LEFTMARGIN="0" ALLOWTRANSPARENCY="true" WIDTH="468" HEIGHT="60"></IFRAME>

    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 35, Column 251: element "IFRAME" undefined
    …N="0" LEFTMARGIN="0" ALLOWTRANSPARENCY="true" WIDTH="468" HEIGHT="60"></IFRAME>

    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 43, Column 30: required attribute "type" not specified
    <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 64, Column 46: there is no attribute "displayText"
    <span class='st_facebook_hcount' displayText='Facebook'></span>

    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 70, 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 70, Column 1: start tag was here
    <br>
  • Error Line 71, 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 71, Column 1: start tag was here
    <br>
  • Error Line 83, 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 83, Column 1: start tag was here
    <br>
  • Error Line 87, Column 7: required attribute "type" not specified
    <style>#web-buttons-idptvb7 a{display:block;color:transparent;} #web-buttons-id…

    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 87, Column 7: document type does not allow element "style" here
    <style>#web-buttons-idptvb7 a{display:block;color:transparent;} #web-buttons-id…

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

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

  • Error Line 89, Column 39: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><t…
  • Error Line 89, Column 53: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …able id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><tr>
  • Error Line 89, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …able id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><tr>
  • Error Line 89, Column 76: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …able id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><tr>
  • Error Line 113, Column 12: ID "web-buttons-idptvb7" already defined
    <table id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><t…

    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 89, Column 12: ID "web-buttons-idptvb7" first defined here
    <table id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><t…
  • Error Line 113, Column 39: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><t…
  • Error Line 113, Column 53: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …able id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><tr>
  • Error Line 113, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …able id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><tr>
  • Error Line 113, Column 76: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …able id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><tr>
  • Error Line 138, 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 138, Column 1: start tag was here
    <br>
  • Error Line 141, Column 12: ID "web-buttons-idptvb7" already defined
    <table id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><t…

    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 89, Column 12: ID "web-buttons-idptvb7" first defined here
    <table id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><t…
  • Error Line 141, Column 39: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><t…
  • Error Line 141, Column 53: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …able id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><tr>
  • Error Line 141, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …able id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><tr>
  • Error Line 141, Column 76: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …able id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><tr>
  • Error Line 145, Column 148: required attribute "alt" not specified
    …t"> <img width="118" height="50" src="images/star_cricket.jpg" > <br/></a></td>

    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 145, Column 149: end tag for "img" omitted, but OMITTAG NO was specified
    …t"> <img width="118" height="50" src="images/star_cricket.jpg" > <br/></a></td>

    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 145, Column 89: start tag was here
    …arget="iframe1" title="Star Cricket"> <img width="118" height="50" src="images…
  • Error Line 149, Column 183: required attribute "alt" not specified
    …c="http://www.pakfriends.pk/images/2012/03/PTV-Sports-Logo.jpg" ><br/></a></td>

    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 149, Column 184: end tag for "img" omitted, but OMITTAG NO was specified
    …c="http://www.pakfriends.pk/images/2012/03/PTV-Sports-Logo.jpg" ><br/></a></td>

    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 149, Column 88: start tag was here
    …target="iframe1" title="PTV Sports" > <img width="118" height="50" src="http:/…
  • Error Line 153, Column 152: required attribute "alt" not specified
    …"> <img width="118" height="50" src="images/willow_cricket.jpg" ><br/></a></td>

    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 153, Column 153: end tag for "img" omitted, but OMITTAG NO was specified
    …"> <img width="118" height="50" src="images/willow_cricket.jpg" ><br/></a></td>

    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 153, Column 91: start tag was here
    …get="iframe1" title="Willow Cricket"> <img width="118" height="50" src="images…
  • Error Line 157, Column 216: required attribute "alt" not specified
    …go7BUo/TjOzGbdHlZI/AAAAAAAAERA/PrP8mbwAk1o/s1600/geo-super.jpg" ><br/></a></td>

    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 157, Column 217: end tag for "img" omitted, but OMITTAG NO was specified
    …go7BUo/TjOzGbdHlZI/AAAAAAAAERA/PrP8mbwAk1o/s1600/geo-super.jpg" ><br/></a></td>

    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 157, Column 87: start tag was here
    … target="iframe1" title="Geo Super" > <img width="118" height="50" src="http:/…
  • Error Line 161, Column 145: required attribute "alt" not specified
    …ts" > <img width="118" height="50" src="images/ten_sports.jpg" > <br/></a></td>

    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 161, Column 146: end tag for "img" omitted, but OMITTAG NO was specified
    …ts" > <img width="118" height="50" src="images/ten_sports.jpg" > <br/></a></td>

    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 161, Column 88: start tag was here
    …target="iframe1" title="Ten Sports" > <img width="118" height="50" src="images…
  • Error Line 169, Column 12: ID "web-buttons-idptvb7" already defined
    <table id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><t…

    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 89, Column 12: ID "web-buttons-idptvb7" first defined here
    <table id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><t…
  • Error Line 169, Column 39: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><t…
  • Error Line 169, Column 53: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …able id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><tr>
  • Error Line 169, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …able id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><tr>
  • Error Line 169, Column 76: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …able id="web-buttons-idptvb7" width=0 cellpadding=0 cellspacing=0 border=0><tr>
  • Error Line 173, Column 145: required attribute "alt" not specified
    …ts"> <img width="118" height="50" src="images/sky_sports1.jpg" > <br/></a></td>

    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 173, Column 146: end tag for "img" omitted, but OMITTAG NO was specified
    …ts"> <img width="118" height="50" src="images/sky_sports1.jpg" > <br/></a></td>

    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 173, Column 87: start tag was here
    … target="iframe1" title="Sky Sports"> <img width="118" height="50" src="images…
  • Error Line 177, Column 154: required attribute "alt" not specified
    …<img width="118" height="35" src="images/sky-sports-2-logo.jpg" ><br/></a></td>

    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 177, Column 155: end tag for "img" omitted, but OMITTAG NO was specified
    …<img width="118" height="35" src="images/sky-sports-2-logo.jpg" ><br/></a></td>

    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 177, Column 90: start tag was here
    …rget="iframe1" title="Sky Sports 2" > <img width="118" height="35" src="images…
  • Error Line 181, Column 159: required attribute "alt" not specified
    …dth="118" height="50" src="images/STAR_Sports_New_logo.svg.png" ><br/></a></td>

    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 181, Column 160: end tag for "img" omitted, but OMITTAG NO was specified
    …dth="118" height="50" src="images/STAR_Sports_New_logo.svg.png" ><br/></a></td>

    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 181, Column 88: start tag was here
    …target="iframe1" title="Star Sports"> <img width="118" height="50" src="images…
  • Error Line 185, Column 139: required attribute "alt" not specified
    …PL 2013" > <img width="118" height="45" src="images/tenact.jpg" ><br/></a></td>

    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 185, Column 140: end tag for "img" omitted, but OMITTAG NO was specified
    …PL 2013" > <img width="118" height="45" src="images/tenact.jpg" ><br/></a></td>

    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 185, Column 86: start tag was here
    …" target="iframe1" title="BPL 2013" > <img width="118" height="45" src="images…
  • Error Line 189, Column 140: required attribute "alt" not specified
    …annel 9" > <img width="120" height="55" src="images/tenhd.jpg" > <br/></a></td>

    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 189, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
    …annel 9" > <img width="120" height="55" src="images/tenhd.jpg" > <br/></a></td>

    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 189, Column 88: start tag was here
    … target="iframe1" title="Channel 9" > <img width="120" height="55" src="images…
  • Warning Line 212, Column 66: reference not terminated by REFC delimiter
    …dmanager.com/st?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_UR…

    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 212, Column 66: reference to external entity in attribute value
    …dmanager.com/st?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_UR…

    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 212, Column 66: reference to entity "ad_size" for which no system identifier could be generated
    …dmanager.com/st?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_UR…

    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 35, Column 58: entity was defined here
    …/ad.yieldmanager.com/st?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=…
  • Warning Line 212, Column 81: reference not terminated by REFC delimiter
    …?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER…

    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 212, Column 81: reference to external entity in attribute value
    …?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER…

    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 212, Column 81: reference to entity "section" for which no system identifier could be generated
    …?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER…

    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 35, Column 73: entity was defined here
    …r.com/st?ad_type=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRA…
  • Warning Line 212, Column 97: reference not terminated by REFC delimiter
    …ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER="0" SCROLLING="…

    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 212, Column 97: reference to external entity in attribute value
    …ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER="0" SCROLLING="…

    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 212, Column 97: reference to entity "pub_url" for which no system identifier could be generated
    …ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER="0" SCROLLING="…

    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 35, Column 89: entity was defined here
    …=iframe&ad_size=468x60&section=4121187&pub_url=${PUB_URL}" FRAMEBORDER="0" SCR…
  • Error Line 212, Column 251: element "IFRAME" undefined
    …N="0" LEFTMARGIN="0" ALLOWTRANSPARENCY="true" WIDTH="468" HEIGHT="60"></IFRAME>

    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 226, Column 20: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="rightad"><div class="ads4">

    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 227, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=300 heigh…
  • Error Line 227, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=300 heigh…
  • Error Line 227, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginwidth=0 marginheight=0 scrolling=no width=300 height=600 src=…
  • Error Line 227, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arginwidth=0 marginheight=0 scrolling=no width=300 height=600 src="http://cric…
  • Error Line 227, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …h=0 marginheight=0 scrolling=no width=300 height=600 src="http://cricket-tv.ne…
  • Error Line 227, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eight=0 scrolling=no width=300 height=600 src="http://cricket-tv.net/chat.html…
  • Error Line 228, Column 336: there is no attribute "allowTransparency"
    …overflow:hidden; width:300px; height:290px;" allowTransparency="true"></iframe>

    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 231, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </li>

    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 226, Column 21: start tag was here
    <li class="rightad"><div class="ads4">
  • Error Line 242, Column 179: end tag for "p" omitted, but OMITTAG NO was specified
    …et-tv.net/" title="Cricket TV">Live Cricket </a>      </div></div> </p>        

    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 242, Column 28: start tag was here
    <div id="footer">          <p> &#169;   <span style="color:#000;">Live Cricket<…
  • Error Line 242, Column 190: end tag for element "p" which is not open
    …et-tv.net/" title="Cricket TV">Live Cricket </a>      </div></div> </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 244, Column 21: required attribute "type" not specified
    <script id="_wau6lu">var _wau = _wau || []; _wau.push(["small", "b7kc7pq7x2j0",…

    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 257, Column 112: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?2113044&101" alt="web hit counter" border="0"><…

    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 257, Column 154: end tag for "img" omitted, but OMITTAG NO was specified
    …histats.com/0.gif?2113044&101" alt="web hit counter" border="0"></a></noscript>

    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 257, Column 60: start tag was here
    …tp://www.histats.com" target="_blank"><img  src="http://sstatic1.histats.com/0…
  • Error Line 260, Column 6: end tag for element "div" which is not open
    </div>

    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.

Visitor Analysis

Daily Visitor
  • 2.800 visits