dinamani.com

Leading Tamil Daily News website delivers Tamil Nadu News, India News, World News, Political News, Business News, Financial News, Cinema & Sports News update. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 04-08-2013 10:47:48  (update).

Overview Info

  • Domain Name
    dinamani.com
  • Favicon
  • Alexa Rank
    #18140
  • Google Page Rank
    PR 6
  • Ip Address
    121.241.226.165
  • Page Size
    125.9 KB
  • Images
    0 GIF, 39 JPG, 16 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 30 14 8 34 2

Website Meta Analysis



  • Title
    Leading Tamil News Paper| Latest Tamil News, India News, World News, Tamil News Paper - Dinamani
  • Meta Keyword
  • Meta Description
    Leading Tamil Daily News website delivers Tamil Nadu News, India News, World News, Political News, Business News, Financial News, Cinema & Sports News update.

Technical Analysis



  • Webserver
    Apache-Coyote/1.1
  • Ip Address
    121.241.226.165
  • Domain Age
    13 Years, 6 Months, 4 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache-Coyote/1.1
  • content-type: text/html;charset=UTF-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-length: 99786
  • accept-ranges: bytes
  • date: Sun, 04 Aug 2013 22:47:43 GMT
  • x-varnish: 1223376615 1223376403
  • via: 1.1 varnish
  • connection: keep-alive
  • x-cache-host: pres1
  • x-cache: HIT #10/17s
  • age: 0
  • x-cache-backend: webdirector
  • x-google-cache-control: remote-fetch
Registrant:
Express Publications LTD
Express Publications LTD Express Publications LTD
29 Express Gardens II Main Road, Ambattur Industrial Estate
Chennai, Tamil Nadu 600058
IN
Phone: +91.914423457601
Email: email

Registrar URL: www.register.com

Domain Name: dinamani.com
Created: 2000-01-11
Expires: 2014-01-11

Administrative Contact:
Express Network Private Limited
Gopalan Nagarajan
29, Express Gardens II Main Road, Ambattur Industrial Estate
Chennai, Tamil Nadu 600058
IN
Phone: +91.4423457601
Email: email

Technical Contact:
Express Network Private Limited
Gopalan Nagarajan
29 Express Gardens II Main Road, Ambattur Industrial Estate
Chennai, Tamil Nadu 600058
IN
Phone: +91.4423457601
Email: email

DNS Servers:
ns1.frontpoint.net
ns2.frontpoint.net

DNS Analysis


DNS servers
dns1.tatacommunicationsdns.com [115.112.250.115]
dns2.tatacommunicationsdns.com [195.219.235.85]


DNS Records

Answer records
dinamani.com TXT v=spf1 a mx include:elabs11.com <http://elabs11.com/> include:netcore.co.in ~all 400s
dinamani.com MX
preference: 10
exchange: mail.dinamani.com
400s
dinamani.com A 121.241.226.165 400s
dinamani.com SOA
server: dns1.tatacommunicationsdns.com
email: msoc@dnsadmin.tatacommunications.com
serial: 2013030700
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
dinamani.com NS  dns2.tatacommunicationsdns.com 86400s
dinamani.com NS  dns3.tatacommunicationsdns.com 86400s
dinamani.com NS  dns4.tatacommunicationsdns.com 86400s
dinamani.com NS  dns1.tatacommunicationsdns.com 86400s
dinamani.com NS  dns5.tatacommunicationsdns.com 86400s

Authority records

Additional records
mail.dinamani.com A 203.197.142.35 400s
dns1.tatacommunicationsdns.com A 115.112.250.115 14400s
dns2.tatacommunicationsdns.com A 195.219.235.85 14400s
dns3.tatacommunicationsdns.com A 209.58.67.115 14400s
dns4.tatacommunicationsdns.com A 66.198.171.70 14400s
dns5.tatacommunicationsdns.com A 121.241.244.165 14400s

IP 121.241.226.165 Analysis

  • Country Code
    IN
  • Country Code3
    IND
  • Country Name
    India
  • City
    Pune
  • Continent Code
    AS
  • Latitude
    18.5333
  • Longitude
    73.8667
  • % [whois.apnic.net node-4]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 121.240.0.0 - 121.247.255.255
    netname: TATACOMM-IN
    descr: Internet Service Provider
    descr: TATA Communications formerly VSNL is Leading ISP,
    descr: Data and Voice Carrier in India
    admin-c: TC651-AP
    tech-c: TC651-AP
    country: IN
    mnt-by: APNIC-HM
    mnt-lower: MAINT-TATACOMM-IN
    mnt-routes: MAINT-TATACOMM-IN
    mnt-irt: IRT-TATACOMM-IN
    status: ALLOCATED PORTABLE
    remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    remarks: This object can only be updated by APNIC hostmasters.
    remarks: To update this object, please contact APNIC
    remarks: hostmasters and include your organisation's account
    remarks: name in the subject line.
    remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    changed: hm-changed@apnic.net 20060814
    changed: hm-changed@apnic.net 20080826
    changed: hm-changed@apnic.net 20080827
    changed: hm-changed@apnic.net 20120221
    source: APNIC

    route: 121.240.0.0/13
    descr: Route for VSNL
    origin: AS4755
    mnt-by: MAINT-VSNL-AP
    changed: ip.admin@vsnl.co.in 20061124
    changed: hm-changed@apnic.net 20080827
    source: APNIC

    role: TATA Communications
    nic-hdl: TC651-AP
    address: 6th Floor, LVSB, VSNL
    address: Kashinath Dhuru marg, Prabhadevi
    address: Dadar(W), Mumbai 400028
    phone: +91-22-56633503
    fax-no: +91-22-24320132
    country: IN
    e-mail: ip.admin@vsnl.co.in
    admin-c: IA15-AP
    tech-c: VT43-AP
    mnt-by: MAINT-TATACOMM-IN
    changed: hm-changed@apnic.net 20080826
    changed: hm-changed@apnic.net 20080827
    source: APNIC


Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 40 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.6392505680452265
Message Error
  • Warning Line 21, Column 172: character "&" is the first character of a delimiter but occurred as data
    … Political News, Business News, Financial News, Cinema & Sports News update."/>

    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 65, Column 18: there is no attribute "language"
    <script language="JavaScript">

    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 65, 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 69, Column 68: required attribute "type" not specified
    <script language="JavaScript" src="http://d3.zedo.com/jsc/d3/fo.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 79, 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 83, Column 68: required attribute "type" not specified
    <script language="JavaScript" src="http://d3.zedo.com/jsc/d3/fo.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 103, Column 8: there is no attribute "target"
    target="_blank">

    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 161, Column 129: there is no attribute "border"
    …llow.png" alt="Follow Us on Facebook" title="Follow Us on Facebook" 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.

  • Error Line 161, Column 133: end tag for "img" omitted, but OMITTAG NO was specified
    …llow.png" alt="Follow Us on Facebook" title="Follow Us on Facebook" border="0">

    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 1: start tag was here
    <img src="http://dinamani.com/skins/dn/gfx/facebookFollow.png" alt="Follow Us o…
  • Error Line 164, Column 130: end tag for "img" omitted, but OMITTAG NO was specified
    …Follow.png" alt="Follow Us on Twitter" title="Follow Us on Twitter" border="0">

    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 164, Column 1: start tag was here
    <img src="http://dinamani.com/skins/dn/gfx/twitterFollow.png" alt="Follow Us on…
  • Error Line 167, Column 129: end tag for "img" omitted, but OMITTAG NO was specified
    …Follow.png" alt="Follow Us on Google+" title="Follow Us on Google+" border="0">

    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 167, Column 1: start tag was here
    <img src="http://dinamani.com/skins/dn/gfx/googleFollow.png" alt="Follow Us on …
  • Warning Line 172, Column 50: cannot generate system identifier for general entity "widgetId"
    …ref="http://dinamani.com/?widgetName=rssfeed&widgetId=1162902&getXmlFeed=true">

    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 172, Column 50: general entity "widgetId" not defined and no default entity
    …ref="http://dinamani.com/?widgetName=rssfeed&widgetId=1162902&getXmlFeed=true">

    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 172, Column 58: reference not terminated by REFC delimiter
    …ref="http://dinamani.com/?widgetName=rssfeed&widgetId=1162902&getXmlFeed=true">

    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 172, Column 58: reference to external entity in attribute value
    …ref="http://dinamani.com/?widgetName=rssfeed&widgetId=1162902&getXmlFeed=true">

    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 172, Column 58: reference to entity "widgetId" for which no system identifier could be generated
    …ref="http://dinamani.com/?widgetName=rssfeed&widgetId=1162902&getXmlFeed=true">

    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 172, Column 49: entity was defined here
    …ref="http://dinamani.com/?widgetName=rssfeed&widgetId=1162902&getXmlFeed=true">
  • Warning Line 172, Column 67: cannot generate system identifier for general entity "getXmlFeed"
    …ref="http://dinamani.com/?widgetName=rssfeed&widgetId=1162902&getXmlFeed=true">

    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 172, Column 67: general entity "getXmlFeed" not defined and no default entity
    …ref="http://dinamani.com/?widgetName=rssfeed&widgetId=1162902&getXmlFeed=true">

    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 172, Column 77: reference not terminated by REFC delimiter
    …ref="http://dinamani.com/?widgetName=rssfeed&widgetId=1162902&getXmlFeed=true">

    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 172, Column 77: reference to external entity in attribute value
    …ref="http://dinamani.com/?widgetName=rssfeed&widgetId=1162902&getXmlFeed=true">

    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 172, Column 77: reference to entity "getXmlFeed" for which no system identifier could be generated
    …ref="http://dinamani.com/?widgetName=rssfeed&widgetId=1162902&getXmlFeed=true">

    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 172, Column 66: entity was defined here
    …ref="http://dinamani.com/?widgetName=rssfeed&widgetId=1162902&getXmlFeed=true">
  • Error Line 789, Column 31: document type does not allow element "script" here; assuming missing "li" start-tag
    <script type="text/javascript">
  • Error Line 801, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

    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 789, Column 1: start tag was here
    <script type="text/javascript">
  • Error Line 806, Column 22: character ")" not allowed in attribute specification list
    if(submenuWidth<width){
  • Error Line 806, Column 22: element "width" undefined
    if(submenuWidth<width){

    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 810, Column 9: end tag for "width" omitted, but OMITTAG NO was specified
    </script>

    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 806, Column 16: start tag was here
    if(submenuWidth<width){
  • Error Line 1086, Column 22: character ")" not allowed in attribute specification list
    if(submenuWidth<width){
  • Error Line 1086, Column 22: element "width" undefined
    if(submenuWidth<width){

    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 1090, Column 9: end tag for "width" omitted, but OMITTAG NO was specified
    </script>

    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 1086, Column 16: start tag was here
    if(submenuWidth<width){
  • Error Line 1100, 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 1102, Column 68: required attribute "type" not specified
    <script language="JavaScript" src="http://d3.zedo.com/jsc/d3/fo.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 1212, Column 23: document type does not allow element "style" here
    <style type="text/css">

    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 1271, Column 101: there is no attribute "onMouseOver"
    …lick="return chicked_1156809('0');" onMouseOver="return chicked_1156809('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.

  • Error Line 1740, 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 1742, Column 68: required attribute "type" not specified
    <script language="JavaScript" src="http://d3.zedo.com/jsc/d3/fo.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 2568, Column 21: there is no attribute "frameborder"
    <iframe frameborder="0" marginwidth="0" marginheight="0" scrolling="no" width="…

    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 2568, Column 37: there is no attribute "marginwidth"
    <iframe frameborder="0" marginwidth="0" marginheight="0" scrolling="no" width="…

    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 2568, Column 54: there is no attribute "marginheight"
    …rder="0" marginwidth="0" marginheight="0" scrolling="no" width="300" src="http…

    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 2568, Column 68: there is no attribute "scrolling"
    …nwidth="0" marginheight="0" scrolling="no" width="300" src="http://www.krishcr…

    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 2568, Column 79: there is no attribute "width"
    …marginheight="0" scrolling="no" width="300" src="http://www.krishcricket.com/o…

    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 2568, Column 89: there is no attribute "src"
    …ht="0" scrolling="no" width="300" src="http://www.krishcricket.com/outsource/s…

    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 2568, Column 164: element "iframe" undefined
    …//www.krishcricket.com/outsource/scorefeeds/dinamani/briefscore.aspx"></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 2580, Column 82: required attribute "alt" not specified
    …g src="http://ichart.finance.yahoo.com/t?s=%5EBSESN" title="Business Quotes" />

    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 2695, Column 12: character "&" is the first character of a delimiter but occurred as data
    if (cookie && /M1432693M/.test("M" + cookie + "M")) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 2695, Column 13: character "&" is the first character of a delimiter but occurred as data
    if (cookie && /M1432693M/.test("M" + cookie + "M")) {

    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 2707, 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 2709, Column 68: required attribute "type" not specified
    <script language="JavaScript" src="http://d3.zedo.com/jsc/d3/fo.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 2986, Column 300: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:300…

    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 2986, Column 377: there is no attribute "allowTransparency"
    …overflow:hidden; width:300px; height:300px;" 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 2986, Column 383: element "iframe" undefined
    …overflow:hidden; width:300px; height:300px;" allowTransparency="true"></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 3021, 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 3047, Column 69: required attribute "type" not specified
    <script charset="utf-8" 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 3049, 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 3249, 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 3251, Column 68: required attribute "type" not specified
    <script language="JavaScript" src="http://d3.zedo.com/jsc/d3/fo.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 3409, 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 3412, Column 68: required attribute "type" not specified
    <script language="JavaScript" src="http://d3.zedo.com/jsc/d3/fo.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>.

Visitor Analysis

Daily Visitor
  • 13.767 visits

In Page Analysis