RSS Home Home Administration Mavrodians Rules MMM CRO RULES Format of tickets LOG-IN into Virtual Account HELP OUR COUNTRY Video SERGEI MAVRODI Instructions for software Seminars Seminars in Bhilai Seminars in Mumbai Seminars ...

mmmindia.in
  • Domain Name
    mmmindia.in
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #5385
  • Page Size
    53.8 KB
  • Ip Address
    193.109.247.68
  • Heading
    H1: 0, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 2 PNG

Website Meta Analysis

  • Title
    MMM INDIA - Mavrodi Mondial Moneybox
  • Meta Keyword
  • Meta Description
    RSS Home Home Administration Mavrodians Rules MMM CRO RULES Format of tickets LOG-IN into Virtual Account HELP OUR COUNTRY Video SERGEI MAVRODI Instructions for software Seminars Seminars in Bhilai Seminars in Mumbai Seminars in Nagpur Seminars ...

Technical Analysis

  • Webserver
    uServ/3.2.2
  • Ip Address
    193.109.247.68
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from mmmindia.in.

HTML Analysis

  • server: uServ/3.2.2
  • date: Tue, 20 Aug 2013 01:05:18 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • cache-control: no-cache
  • pragma: no-cache
  • vary: host
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Access to .IN WHOIS information is provided to assist persons in
determining the contents of a domain name registration record in the
.IN registry database. The data in this record is provided by
.IN Registry for informational purposes only, and .IN does not
guarantee its accuracy. This service is intended only for query-based
access. You agree that you will use this data only for lawful purposes
and that, under no circumstances will you use this data to: (a) allow,
enable, or otherwise support the transmission by e-mail, telephone, or
facsimile of mass unsolicited, commercial advertising or solicitations
to entities other than the data recipient's own existing customers; or
(b) enable high volume, automated, electronic processes that send
queries or data to the systems of Registry Operator, a Registrar, or
Afilias except as reasonably necessary to register domain names or
modify existing registrations. All rights reserved. .IN reserves
the right to modify these terms at any time. By submitting this query,
you agree to abide by this policy.

Domain ID:D6628613-AFIN
Domain Name:MMMINDIA.IN
Created On:11-Jul-2012 12:05:45 UTC
Last Updated On:18-Oct-2012 23:39:22 UTC
Expiration Date:11-Jul-2013 12:05:45 UTC
Sponsoring Registrar:Directi Web Services Pvt. Ltd. (R118-AFIN)
Status:CLIENT TRANSFER PROHIBITED
Registrant ID:DI_23167181
Registrant Name:3234807
Registrant Organization:Private Person
Registrant Street1:169347, Russia, Komi Respublika, Ukhta, pos.Yarega, ulitsa
Registrant Street2:Neftnyakov, d.4a, kv.75
Registrant Street3:
Registrant City:Ukhta, pos.Yarega
Registrant State/Province:Komi Respublika
Registrant Postal Code:169347
Registrant Country:RU
Registrant Phone:+7.9252839299
Registrant Phone Ext.:
Registrant FAX:
Registrant FAX Ext.:
Registrant Email: email
Admin ID:DI_23167182
Admin Name:3234807
Admin Organization:Private Person
Admin Street1:169347, Russia, Komi Respublika, Ukhta, pos.Yarega, ulitsa
Admin Street2:Neftnyakov, d.4a, kv.75
Admin Street3:
Admin City:Ukhta, pos.Yarega
Admin State/Province:Komi Respublika
Admin Postal Code:169347
Admin Country:RU
Admin Phone:+7.9252839299
Admin Phone Ext.:
Admin FAX:
Admin FAX Ext.:
Admin Email: email
Tech ID:DI_23167183
Tech Name:3234807
Tech Organization:Private Person
Tech Street1:169347, Russia, Komi Respublika, Ukhta, pos.Yarega, ulitsa
Tech Street2:Neftnyakov, d.4a, kv.75
Tech Street3:
Tech City:Ukhta, pos.Yarega
Tech State/Province:Komi Respublika
Tech Postal Code:169347
Tech Country:RU
Tech Phone:+7.9252839299
Tech Phone Ext.:
Tech FAX:
Tech FAX Ext.:
Tech Email: email
Name Server:NS1.DEPOTELECOM.RU
Name Server:NS2.DEPOTELECOM.RU
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
DNSSEC:Unsigned


DNS Analysis


DNS servers
ns1.depotelecom.ru [193.169.179.2]
ns2.depotelecom.ru [82.146.35.181]


DNS Records

Answer records
mmmindia.in SOA
server: ns1.depotelecom.ru
email: support@depotelecom.ru
serial: 2012071306
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
3600s
mmmindia.in NS  ns1.depotelecom.ru 3600s
mmmindia.in NS  ns2.depotelecom.ru 3600s
mmmindia.in A 193.109.247.68 3600s
mmmindia.in MX
preference: 20
exchange: mail.mmmindia.in
3600s
mmmindia.in MX
preference: 10
exchange: mail.mmmindia.in
3600s
mmmindia.in TXT v=spf1 ip4:193.169.179.2 a mx ~all 3600s

Authority records

Additional records
ns1.depotelecom.ru A 193.169.179.2 3600s
ns2.depotelecom.ru A 82.146.35.181 3600s
mail.mmmindia.in A 193.109.247.68 3600s

IP 193.109.247.68 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 61 Errors
  • 8 Warnings
Ratio Text/Html
  • 0.6504273039028905
Message Error
  • Error Line 2, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Warning Line 8, Column 59: NET-enabling start-tag requires SHORTTAG YES
    <link type="text/css" rel="StyleSheet" href="/_st/my.css" /> 

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

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

  • Warning Line 9, Column 82: NET-enabling start-tag requires SHORTTAG YES
    …k type="text/css" rel="StyleSheet" href="http://s68.ucoz.net/src/layer2.css" />

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

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

  • Error Line 9, Column 82: document type does not allow element "LINK" here
    …k type="text/css" rel="StyleSheet" href="http://s68.ucoz.net/src/layer2.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).

  • Warning Line 11, Column 95: NET-enabling start-tag requires SHORTTAG YES
    …css" rel="stylesheet" type="text/css" /><script type="text/javascript" src="ht…

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

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

  • Error Line 11, Column 95: document type does not allow element "LINK" here
    …css" rel="stylesheet" type="text/css" /><script type="text/javascript" src="ht…

    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 12, Column 103: document type does not allow element "STYLE" here
    …c/uwnd.js?2"></script><style type="text/css">.UhideBlock {display:none}</style>

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

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

  • Error Line 13, Column 7: end tag for element "HEAD" which is not open
    </head>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 14, Column 6: document type does not allow element "BODY" here
    <body>

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

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

  • Error Line 27, Column 77: required attribute "ALT" not specified
    …a href="/"><img src="/img/logo.png" title="MMM-INDIA" style="height:162px"></a>

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

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

  • Error Line 90, Column 25: there is no attribute "ALLOWFULLSCREEN"
    <iframe allowfullscreen="" frameborder="0" height="315" src="http://www.youtube…

    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 91, Column 112: "ALLOWFULLSCREEN" is not a member of a group specified for any attribute
    …YkDqQ" frameborder="0" allowfullscreen></iframe><p style="margin: 10px 0px; pa…
  • Warning Line 214, Column 38: cannot generate system identifier for general entity "u_data"
    <a href="http://memori.ru/link/?sm=1&u_data[url]=http://mmmindia.in/" rel="nofo…

    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 214, Column 38: general entity "u_data" not defined and no default entity
    <a href="http://memori.ru/link/?sm=1&u_data[url]=http://mmmindia.in/" rel="nofo…

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

  • Error Line 214, Column 44: reference to entity "u_data" for which no system identifier could be generated
    …ef="http://memori.ru/link/?sm=1&u_data[url]=http://mmmindia.in/" rel="nofollow…

    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 214, Column 37: entity was defined here
    <a href="http://memori.ru/link/?sm=1&u_data[url]=http://mmmindia.in/" rel="nofo…
  • Error Line 231, Column 47: required attribute "ALT" not specified
     <img src="/am.png" title="MR. ALEXEI MURATOV"><br>

    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 270, Column 8: required attribute "TYPE" not specified
     <style>

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

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

  • Error Line 270, Column 8: document type does not allow element "STYLE" here
     <style>

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

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

  • Error Line 273, Column 173: there is no attribute "LASTNEWS"
    …idth="100%" class="infTable" lastnews="true"><tbody><tr><td class="infTitle" c…

    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 273, Column 179: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …100%" class="infTable" lastnews="true"><tbody><tr><td class="infTitle" colspan…

    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 273, Column 455: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …100%" class="infTable" lastnews="true"><tbody><tr><td class="infTitle" colspan…

    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 273, Column 719: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …100%" class="infTable" lastnews="true"><tbody><tr><td class="infTitle" colspan…

    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 273, Column 963: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …100%" class="infTable" lastnews="true"><tbody><tr><td class="infTitle" colspan…

    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 273, Column 1204: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …100%" class="infTable" lastnews="true"><tbody><tr><td class="infTitle" colspan…

    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 290, Column 9: required attribute "TYPE" not specified
     <script>(function(d, s, 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 297, Column 37: there is no attribute "DATA-HREF"
     <div class="fb-like-box" data-href="https://www.facebook.com/pages/MMM-India-M…

    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 297, Column 132: there is no attribute "DATA-WIDTH"
    …-Moneybox/332237150194640" data-width="237" data-show-faces="true" data-border…

    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 297, Column 154: there is no attribute "DATA-SHOW-FACES"
    …640" data-width="237" data-show-faces="true" data-border-color="#e5e5e5" data-…

    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 297, Column 179: there is no attribute "DATA-BORDER-COLOR"
    …a-show-faces="true" data-border-color="#e5e5e5" data-stream="false" data-heade…

    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 297, Column 201: there is no attribute "DATA-STREAM"
    …true" data-border-color="#e5e5e5" data-stream="false" data-header="true"></div>

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

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

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

  • Error Line 297, Column 221: there is no attribute "DATA-HEADER"
    …true" data-border-color="#e5e5e5" data-stream="false" data-header="true"></div>

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

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

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

Visitor Analysis

Daily Visitor
  • 10.267 visits