clasicooo.com

clasicooo.com

[ موقع ريال مدريد - موقع برشلونة - موقع انتر ميلان - موقع اي سي ميلان - موقع النصر السعودي - موقع الهلال السعودي - منتديات هاي ياعرب ] سياسة الخصوصية - Privacy ...

Domain Name clasicooo.com
Favicon clasicooo.com
Google Page Rank 4
Alexa Rank #5268
Page Size 6 KB
Ip Address 31.24.224.179
Heading H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
Images 0 GIF, 7 JPG, 0 PNG

Website Meta Analysis

Title مرحبا بكم في شبكة الكلاسيكو العربية
Meta Keyword
Meta Description [ موقع ريال مدريد - موقع برشلونة - موقع انتر ميلان - موقع اي سي ميلان - موقع النصر السعودي - موقع الهلال السعودي - منتديات هاي ياعرب ] سياسة الخصوصية - Privacy Policy اعلن معنا - advertise with us

Technical Analysis

Webserver nginx admin
Ip Address 31.24.224.179
Domain Age
Javascript Library
Language used HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx admin
  • date: Mon, 11 Mar 2013 16:19:33 GMT
  • content-type: text/html
  • connection: keep-alive
  • vary: Accept-Encoding
  • last-modified: Wed, 06 Mar 2013 08:37:51 GMT
  • x-cache: HIT from Backend
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

No data whois for clasicooo.com

Technical Analysis


DNS servers
ns15.920022033.com [31.24.224.180]
ns16.920022033.com [31.24.224.181]

DNS Records

Answer records
clasicooo.com MX
preference: 0
exchange: clasicooo.com
900s
clasicooo.com TXT v=spf1 ip4:31.24.224.179 a ?all 900s
clasicooo.com SOA
server: ns16.920022033.com
email: support@1net.net.sa
serial: 2012012105
refresh: 1200
retry: 120
expire: 1209600
minimum ttl: 900
900s
clasicooo.com NS  ns16.920022033.com 86400s
clasicooo.com NS  ns15.920022033.com 86400s
clasicooo.com A 31.24.224.179 900s

Authority records

Additional records
clasicooo.com A 31.24.224.179 900s
ns15.920022033.com A 31.24.224.180 14400s
ns16.920022033.com A 31.24.224.181 14400s

IP 31.24.224.179 Analysis

Country Code : SA
Country Code3 : SAU
Country Name : Saudi Arabia
City : AS
Continent Code : 25° North
Latitude : 45.
Longitude :

No whois ip data for 31.24.224.179

In Page Analysis

Traffic Analysis

Magestic Backlinks

Daily Ranks

Rank Trend

Visitor Trend

Bounce Trend

HTML Analysis

HTML validation
  • 18 Errors
  • 15 Warnings
Ratio Text/Html

0.4793214862681745

Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html dir="rtl">

    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 79: NET-enabling start-tag requires SHORTTAG YES
    <meta name="verify-v1" content="S0QWUYngzI9cw4lwoiLfnffWAFrZRjoDz+Kw26g+pts=" />

    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 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 64, 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 66, Column 67: document type does not allow element "BODY" here
    <body bgcolor="#000000" onload="slideMenu.build('sm',200,10,10,1)">

    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 68, Column 5: NET-enabling start-tag requires SHORTTAG YES
    <br />

    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 72, 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 75, Column 68: required attribute "TYPE" not specified
    <script language="JavaScript" src="http://c5.zedo.com/jsc/c5/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>.

  • Warning Line 84, Column 36: NET-enabling start-tag requires SHORTTAG YES
        <img src="images/w.jpg" alt="" />

    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 90, Column 89: NET-enabling start-tag requires SHORTTAG YES
    …/www.clasicooo.com/real/"><img src="images/1.jpg" alt="" border="0" /></a></li>

    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 91, Column 90: NET-enabling start-tag requires SHORTTAG YES
    …www.clasicooo.com/barca/"><img src="images/2.jpg" alt="" border="0" /></a></li>

    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 92, Column 90: NET-enabling start-tag requires SHORTTAG YES
    …www.clasicooo.com/inter/"><img src="images/3.jpg" alt="" border="0" /></a></li>

    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 93, Column 90: NET-enabling start-tag requires SHORTTAG YES
    …www.clasicooo.com/milan/"><img src="images/4.jpg" alt="" border="0" /></a></li>

    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 94, Column 86: NET-enabling start-tag requires SHORTTAG YES
    …p://nassr.clasicooo.com/"><img src="images/5.jpg" alt="" border="0" /></a></li>

    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 95, Column 86: NET-enabling start-tag requires SHORTTAG YES
    …p://hilal.clasicooo.com/"><img src="images/6.jpg" alt="" border="0" /></a></li>

    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 114, 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 117, Column 68: required attribute "TYPE" not specified
    <script language="JavaScript" src="http://c5.zedo.com/jsc/c5/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>.

  • Warning Line 130, Column 65: cannot generate system identifier for general entity "pa"
    …ooo.com/real/modules.php?name=Content&pa=showpage&pid=3" target="_blank">سياسة…

    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 130, Column 65: general entity "pa" not defined and no default entity
    …ooo.com/real/modules.php?name=Content&pa=showpage&pid=3" target="_blank">سياسة…

    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 130, Column 67: reference to entity "pa" for which no system identifier could be generated
    …o.com/real/modules.php?name=Content&pa=showpage&pid=3" target="_blank">سياسة ا…

    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 130, Column 64: entity was defined here
    …cooo.com/real/modules.php?name=Content&pa=showpage&pid=3" target="_blank">سياس…
  • Warning Line 130, Column 77: cannot generate system identifier for general entity "pid"
    …/modules.php?name=Content&pa=showpage&pid=3" target="_blank">سياسة الخصوصية - …

    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 130, Column 77: general entity "pid" not defined and no default entity
    …/modules.php?name=Content&pa=showpage&pid=3" target="_blank">سياسة الخصوصية - …

    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 130, Column 80: reference to entity "pid" for which no system identifier could be generated
    …dules.php?name=Content&pa=showpage&pid=3" target="_blank">سياسة الخصوصية - Pri…

    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 130, Column 76: entity was defined here
    …l/modules.php?name=Content&pa=showpage&pid=3" target="_blank">سياسة الخصوصية -…
  • Error Line 131, Column 67: reference to entity "pa" for which no system identifier could be generated
    …o.com/real/modules.php?name=Content&pa=showpage&pid=19" target="_blank">اعلن م…

    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 130, Column 64: entity was defined here
    …cooo.com/real/modules.php?name=Content&pa=showpage&pid=3" target="_blank">سياس…
  • Error Line 131, Column 80: reference to entity "pid" for which no system identifier could be generated
    …dules.php?name=Content&pa=showpage&pid=19" target="_blank">اعلن معنا - adverti…

    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 130, Column 76: entity was defined here
    …l/modules.php?name=Content&pa=showpage&pid=3" target="_blank">سياسة الخصوصية -…
  • Error Line 136, 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 139, Column 68: required attribute "TYPE" not specified
    <script language="JavaScript" src="http://c5.zedo.com/jsc/c5/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>.

  • Warning Line 144, Column 5: NET-enabling start-tag requires SHORTTAG YES
    <br /><br />

    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 144, Column 11: NET-enabling start-tag requires SHORTTAG YES
    <br /><br />

    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.

Visitor Analysis

Daily Visitor

26.833 visits

Daily Visitor