مدهش - موقع مدينة مدهش الترفيهية - شبكة و موقع عالم مدهش دبي - العاب مدهش - يوتيوب مدهش - صور مدهشة - صيف دبي - دليل مدهش - موقع تسلية و ترفيه ...

o2u1.com
  • Domain Name
    o2u1.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #58492
  • Page Size
    11 KB
  • Ip Address
    178.63.44.131
  • Heading
    H1: 1, H2: 2, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 1 JPG, 0 PNG

Website Meta Analysis

  • Title
    مدهش - موقع مدينة مدهش الترفيهية - عالم مدهش
  • Meta Keyword
    مدهش - موقع مدينة مدهش الترفيهية - شبكة و موقع عالم مدهش دبي - العاب مدهش - يوتيوب مدهش - صور مدهشة - صيف دبي - دليل مدهش - موقع تسلية و ترفيه
  • Meta Description
    مدهش - موقع مدينة مدهش الترفيهية - شبكة و موقع عالم مدهش دبي - العاب مدهش - يوتيوب مدهش - صور مدهشة - صيف دبي - دليل مدهش - موقع تسلية و ترفيه

Technical Analysis

  • Webserver
    nginx/1.2.2
  • Ip Address
    178.63.44.131
  • Domain Age
    3 Years, 6 Months, 14 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.2.2
  • date: Sat, 23 Feb 2013 20:03:05 GMT
  • content-type: text/html
  • content-length: 9499
  • connection: keep-alive
  • last-modified: Tue, 09 Oct 2012 11:11:46 GMT
  • etag: "2d030d6-251b-4cb9e67590080"
  • accept-ranges: bytes
  • age: 12
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
No data whois for o2u1.com

DNS Analysis


DNS servers
ns1.a7la3lm.com [178.63.44.131]
ns2.a7la3lm.com [178.63.44.131]


DNS Records

Answer records
o2u1.com MX
preference: 10
exchange: 1024868647.pamx1.hotmail.com
14400s
o2u1.com SOA
server: ns1.a7la3lm.com
email: hamdi@topteam.ps
serial: 2012101600
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
o2u1.com NS  ns2.a7la3lm.com 86400s
o2u1.com NS  ns1.a7la3lm.com 86400s
o2u1.com A 178.63.44.131 14400s

Authority records

Additional records
ns1.a7la3lm.com A 178.63.44.131 14400s
ns2.a7la3lm.com A 178.63.44.131 14400s

IP 178.63.44.131 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 7 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.6475453575240129
Message Error
  • Error Line 3, Column 21: there is no attribute "XMLNS"
    <HTML dir=rtl xmlns="http://www.w3.org/1999/xhtml"><HEAD><TITLE>مدهش - موقع 

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

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

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

  • Warning Line 13, Column 10: NET-enabling start-tag requires SHORTTAG YES
    type=text/css href="http://www.o2u1.com/o2u1-2009/style.css" media=screen>

    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 14, Column 18: NET-enabling start-tag requires SHORTTAG YES
    <SCRIPT type=text/javascript>

    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 22, Column 18: NET-enabling start-tag requires SHORTTAG YES
    <SCRIPT type=text/javascript>

    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 36, Column 7: 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 36, Column 7: 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 48, Column 7: end tag for element "HEAD" which is not open
    </HEAD><BODY><!-- wrap starts here -->

    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 48, Column 13: document type does not allow element "BODY" here
    </HEAD><BODY><!-- wrap starts here -->

    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 83, Column 53: there is no attribute "HEIGHT"
    <TABLE id=AutoNumber10 border=0 width="100%" height="122">

    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 261, Column 111: there is no attribute "LOWSRC"
    …: 0px" width="130" height="92" lowsrc="مجلة%20ديارنا" longdesc="مجلة ديارنا" a…

    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
  • 2.217 visits
Daily Visitor