الموقع الرسمي لصحيفة قوون الرياضية السودانية ...

goansport.net
  • Domain Name
    goansport.net
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #16197
  • Page Size
    55.6 KB
  • Ip Address
    198.15.119.10
  • Heading
    H1: 0, H2: 16, H3: 6, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 23 JPG, 1 PNG

Website Meta Analysis

  • Title
    الموقع الرسمي لصحيفة قوون |
  • Meta Keyword
    كرة قدم ،السودان،قوون،صحف سودانية ، المريخ،الهلال،الموردة،الدوري ممتاز،الاتحاد صور مصر ،اخبار الاهلي الزعيم الهلال اليوم شبكة منتدى منتديات المريخ, كرة قدم ،السودان،قوون،صحف سودانية ، المريخ،الهلال،الموردة،الدوري ممتاز،الاتحاد صور مصر ،اخبار الاهلي الزعيم الهلال اليوم شبكة منتدى منتديات المريخ ، صحف سودانية ، صحيفة قوون ، قوون ، قوون الرياضية ، قناة قوون
  • Meta Description
    الموقع الرسمي لصحيفة قوون الرياضية السودانية

Technical Analysis

  • Webserver
    - Web acceleration by http://www.unixy.net/varnish
  • Ip Address
    198.15.119.10
  • Domain Age
    9 Years, 5 Months, 27 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from goansport.net.

HTML Analysis

  • x-powered-by: PHP/5.3.18
  • cache-control: store, no-cache, must-revalidate, post-check=0, pre-check=0
  • last-modified: Thu, 28 Feb 2013 13:36:15 GMT
  • content-type: text/html; charset=utf-8
  • server: - Web acceleration by http://www.unixy.net/varnish
  • x-cacheable: YES
  • content-length: 57579
  • accept-ranges: bytes
  • date: Thu, 28 Feb 2013 13:36:26 GMT
  • x-varnish: 1763687563 1763687457
  • via: 1.1 varnish
  • connection: keep-alive
  • age: 0
  • x-cache: HIT
  • x-cache-hits: 1
  • x-google-cache-control: remote-fetch
No data whois for goansport.net

DNS Analysis


DNS servers
best1.sudabest.net [198.15.119.10]
best2.sudabest.net [198.15.119.11]


DNS Records

Answer records
goansport.net MX
preference: 0
exchange: goansport.net
14400s
goansport.net SOA
server: best1.sudabest.net
email: sudabest@yahoo.com
serial: 2012111203
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
goansport.net NS  best2.sudabest.net 86400s
goansport.net NS  best1.sudabest.net 86400s
goansport.net A 198.15.119.10 14400s

Authority records

Additional records
goansport.net A 198.15.119.10 14400s

IP 198.15.119.10 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • %rwhois V-1.0,V-1.5:00090h:00 portal.phoenixnap.com (Ubersmith RWhois Server V-2.2.0)
    autharea=198.15.64.0/18
    xautharea=198.15.64.0/18
    network:Class-Name:network
    network:Auth-Area:198.15.64.0/18
    network:ID:NET-33432.198.15.119.8/29
    network:Network-Name:Public
    network:IP-Network:198.15.119.8/29
    network:IP-Network-Block:198.15.119.8 - 198.15.119.15
    network:Org-Name:MahgoubYassin
    network:Street-Address:ALSALAM STREET - ALSALAMA Tower - Ap. 704
    network:City:ABUDHABI
    network:State:AZ
    network:Postal-Code:372
    network:Country-Code:AE
    network:Tech-Contact:MAINT-33432.198.15.119.8/29
    network:Created:20121109163039000
    network:Updated:20121109163039000
    network:Updated-By:dnsadmin@securedservers.com
    contact:POC-Name:DNS Administrator
    contact:POC-Email:dnsadmin@securedservers.com
    contact:POC-Phone:(480) 422-2023
    contact:Tech-Name:DNS Administrator
    contact:Tech-Email:dnsadmin@securedservers.com
    contact:Tech-Phone:(480) 422-2023
    contact:Abuse-Name:Abuse
    contact:Abuse-Email:abuse@securedservers.com
    contact:Abuse-Phone:+1-480-422-2022 (Office)
    %ok

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 18 Errors
  • 0 Warnings
Ratio Text/Html
  • 0.6223593096418152
Message Error
  • Error Line 286, Column 171: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D8%A7%D8%A1-%D9%83%D9%84-%D9%8A%D9%88%D9%85"><p>رمضان احمد السيد</p></a></span>

    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 299, Column 183: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …B7%D8%A7%D9%84-%D8%A7%D9%84%D8%B3%D9%81%D8%B1"><p>محمد عبدالماجد</p></a></span>

    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 312, Column 170: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D8%AE%D9%84%D9%81-%D8%A7%D9%84%D8%B4%D8%A8%D8%A7%D9%83"><p>كبوتش</p></a></span>

    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 325, Column 158: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …/%D8%AE%D8%B7-%D9%85%D8%A8%D8%A7%D8%B4%D8%B1"><p>احمد الحاج مكي </p></a></span>

    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 338, Column 151: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …%AF%D8%A9/%D9%83%D9%8A%D8%A8%D9%88%D8%B1%D8%AF"><p>الطيب علي فرح</p></a></span>

    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 351, Column 188: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …1-%D9%88%D8%AA%D8%B9%D9%84%D9%8A%D9%82%D8%A7%D8%AA"><p>عبده قابل</p></a></span>

    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 572, Column 63: required attribute "type" not specified
    …ect.facebook.net/en_US/all.js#xfbml=1"></script><p><fb:like-box border_color="…

    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 572, Column 102: there is no attribute "border_color"
    …</script><p><fb:like-box border_color="" header="true" href="http://www.facebo…

    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 572, Column 112: there is no attribute "header"
    …p><fb:like-box border_color="" header="true" href="http://www.facebook.com/Goa…

    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 572, Column 124: there is no attribute "href"
    …ox border_color="" header="true" href="http://www.facebook.com/Goansport.net" …

    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 572, Column 175: there is no attribute "show_faces"
    …acebook.com/Goansport.net" show_faces="true" stream="false" width="277"></fb:l…

    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 572, Column 189: there is no attribute "stream"
    …/Goansport.net" show_faces="true" stream="false" width="277"></fb:like-box></p>

    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 572, Column 203: there is no attribute "width"
    …/Goansport.net" show_faces="true" stream="false" width="277"></fb:like-box></p>

    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 572, Column 208: element "fb:like-box" undefined
    …/Goansport.net" show_faces="true" stream="false" width="277"></fb:like-box></p>

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

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 607, Column 3: start tag was here
      <div class="views-field-teaser">
  • Error Line 763, Column 101: end tag for "span" omitted, but OMITTAG NO was specified
    …gb(0, 0, 0); font-family: 'Times New Roman'; font-size: medium;">حاوره...</div>

    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 763, Column 2: start tag was here
    	<span style="color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: m…
  • Error Line 765, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 761, Column 3: start tag was here
      <div class="views-field-teaser">
  • Error Line 844, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 838, Column 3: start tag was here
      <div class="views-field-teaser">

Visitor Analysis

Daily Visitor
  • 13.183 visits
Daily Visitor