超人氣休閒娛樂論壇,包含品味生活、休閒天地、興趣嗜好、學術藝文、女性頻道、電腦數位、遊戲天堂、影視音樂、宗教綜合、綜合圖片、綜合影片、成人園地...等一百多個討論區,內容包羅萬象,應有盡有。SOGO論壇是您放鬆心情,抒解壓力的好地方。 sogox我們的論壇,sogo,百貨,sogou論壇 ...

oursogo.com
  • Domain Name
    oursogo.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #9530
  • Page Size
    110.7 KB
  • Ip Address
    190.93.255.80
  • Heading
    H1: 0, H2: 11, H3: 1, H4: 0, H5: 0, H6: 0
  • Images
    18 GIF, 76 JPG, 5 PNG

Website Meta Analysis

  • Title
    SOGO論壇–我們的論壇,大家的論壇 OURSOGO.COM
  • Meta Keyword
    SOGO,SOGO論壇,論壇,討論區,bbs,sogox我們的論壇,sogox,sogou論壇,sogou,sogo百貨,生活,聊天,休閒,愛情,婚姻,家庭,法律,宗教,興趣,旅遊,時尚,美食,汽車,機車,釣魚,星座,命理,寵物,小說,嗜好,布袋戲,園藝,花卉,軍事,藝術,模型,魔術,百貨,消費,購物,省錢,女性,彩妝,內衣,珠寶,首飾,時裝,美髮,電腦,數位,3c,軟體,硬體,燒錄,網際網路,程式設計,手機,攝影,遊戲,TV GAME,PC GAME,ONLINE GAME,FLASH GAME,投資,財經,股票,基金,外匯,期貨,房地產,信用卡,貸款,壽險,產險,理財,創業,退休,防癌,中醫,養生,抗癌,醫療,保健,學術,藝文,歷史,科學,考試,電影,電視,戲劇,音樂,舞蹈,娛樂
  • Meta Description
    超人氣休閒娛樂論壇,包含品味生活、休閒天地、興趣嗜好、學術藝文、女性頻道、電腦數位、遊戲天堂、影視音樂、宗教綜合、綜合圖片、綜合影片、成人園地...等一百多個討論區,內容包羅萬象,應有盡有。SOGO論壇是您放鬆心情,抒解壓力的好地方。 sogox我們的論壇,sogo,百貨,sogou論壇

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    190.93.255.80
  • Domain Age
    7 Years, 12 Months, 5 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Mon, 13 Oct 2014 09:53:32 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • x-powered-by: PHP/5.4.20
  • vary: Accept-Encoding
  • cache-control: max-age=0
  • expires: Mon, 13 Oct 2014 09:53:32 GMT
  • server: cloudflare-nginx
  • cf-ray: 178aa69337710418-ORD
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States

Domain Name: OURSOGO.COM
Created on: 28-Jul-05
Expires on: 28-Jul-16
Last Updated on: 03-Jul-11

Administrative Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Technical Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Domain servers in listed order:
NS1186.DNS.DYN.COM
NS2131.DNS.DYN.COM
NS3185.DNS.DYN.COM
NS4131.DNS.DYN.COM

DNS Analysis


DNS servers
ns1186.dns.dyn.com [208.76.58.186]
ns2131.dns.dyn.com [208.76.59.131]
ns3185.dns.dyn.com [208.76.60.185]
ns4131.dns.dyn.com [208.76.61.131]


DNS Records

Answer records
oursogo.com SOA
server: ns1.mydyndns.org
email: zone-admin@dyndns.com
serial: 2011060720
refresh: 10800
retry: 1800
expire: 604800
minimum ttl: 1800
86400s
oursogo.com NS  ns3185.dns.dyn.com 86400s
oursogo.com NS  ns1186.dns.dyn.com 86400s
oursogo.com NS  ns4131.dns.dyn.com 86400s
oursogo.com NS  ns2131.dns.dyn.com 86400s
oursogo.com A 50.23.85.172 3600s
oursogo.com MX
preference: 10
exchange: mail.oursogo.com
3600s
oursogo.com TXT v=spf1 a mx ip4:50.23.69.107 ?all 3600s

Authority records

Additional records
mail.oursogo.com A 50.23.85.172 3600s

IP 190.93.255.80 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 148 Errors
  • 17 Warnings
Ratio Text/Html
  • 0.6732158131905925
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html><head><title>&#x9801;&#x9762;&#x91CD;&#x8F09;&#x958B;&#x555F;</title></he…

    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.

  • Error Line 1, Column 136: required attribute "TYPE" not specified
    …#FFFFFF"><script language="JavaScript">function reload() {	document.location.r…

    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 1, Column 307: there is no attribute "HEIGHT"
    …"0" width="700" align="center" height="85%">  <tr align="center" valign="middl…

    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 1, Column 587: NET-enabling start-tag requires SHORTTAG YES
    …="center" bgcolor="#EBEBEB">     	<br /><br /> <b style="font-size: 16px">&#x9…

    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 1, Column 593: NET-enabling start-tag requires SHORTTAG YES
    …er" bgcolor="#EBEBEB">     	<br /><br /> <b style="font-size: 16px">&#x9801;&#…

    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 1, Column 680: NET-enabling start-tag requires SHORTTAG YES
    …91CD;&#x8F09;&#x958B;&#x555F;</b> <br /><br />&#x6B61;&#x8FCE;&#x5149;&#x81E8;…

    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 1, Column 686: NET-enabling start-tag requires SHORTTAG YES
    …#x8F09;&#x958B;&#x555F;</b> <br /><br />&#x6B61;&#x8FCE;&#x5149;&#x81E8;&#x672…

    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 1, Column 855: NET-enabling start-tag requires SHORTTAG YES
    …#x8ACB;&#x7A0D;&#x5019;...        <br /><br />      </td>    </tr>    </table>…

    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 1, Column 861: NET-enabling start-tag requires SHORTTAG YES
    …;&#x7A0D;&#x5019;...        <br /><br />      </td>    </tr>    </table>    </…

    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
  • 14.000 visits