graphis.ne.jp

graphis.ne.jp has Alexa Rank 61.319 and Google Page Rank is 2

Display Widget for this domain on your website. Click Here
This data was last updated from 09-08-2013 10:30:23  (update).

Overview Info

  • Domain Name
    graphis.ne.jp
  • Favicon
  • Alexa Rank
    #61319
  • Google Page Rank
    PR 2
  • Ip Address
    211.13.210.124
  • Page Size
    2.4 KB
  • Images
    0 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    WELCOME TO GRAPHIS
  • Meta Keyword
  • Meta Description

Technical Analysis



  • Webserver
    Apache/2.2.23 (Unix) PHP/5.3.17
  • Ip Address
    211.13.210.124
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from graphis.ne.jp.

HTML Analysis

  • date: Fri, 09 Aug 2013 10:30:20 GMT
  • server: Apache/2.2.23 (Unix) PHP/5.3.17
  • last-modified: Tue, 12 Mar 2013 02:47:23 GMT
  • etag: "6ab035-9a6-4d7b14f1804c0"
  • accept-ranges: bytes
  • content-length: 2470
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
[ JPRS database provides information on network administration. Its use is ]
[ restricted to network administration purposes. For further information, ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]

Domain Information:
a. [Domain Name] GRAPHIS.NE.JP
d. [Network Service Name] GRAPHIS
l. [Organization Type] Network Service
m. [Administrative Contact] HT5439JP
n. [Technical Contact] HT5439JP
p. [Name Server] ns1.shard.jp
p. [Name Server] ns2.shard.jp
s. [Signing Key]
[State] Connected (2012/11/30)
[Registered Date] 2001/11/28
[Connected Date] 2002/01/15
[Last Update] 2011/12/01 01:19:29 (JST)

DNS Analysis


DNS servers
ns1.shard.jp [202.181.108.70]
ns2.shard.jp [202.181.108.71]


DNS Records

Answer records
graphis.ne.jp SOA
server: ns1.shard.jp
email: nic-admin@shard.jp
serial: 2012102301
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
3600s
graphis.ne.jp A 211.13.210.124 3600s
graphis.ne.jp NS  ns2.shard.jp 172800s
graphis.ne.jp NS  ns1.shard.jp 172800s
graphis.ne.jp MX
preference: 10
exchange: mail.graphis.ne.jp
3600s

Authority records

Additional records
ns1.shard.jp A 202.181.108.70 172800s
ns2.shard.jp A 202.181.108.71 172800s
mail.graphis.ne.jp A 211.13.210.124 3600s

IP 211.13.210.124 Analysis

  • Country Code
    JP
  • Country Code3
    JPN
  • Country Name
    Japan
  • City
    AS
  • Continent Code
    36° North
  • Latitude
    138.
  • Longitude

  • Network Information:
    a. [Network Number] 211.13.210.0/25
    b. [Network Name] CV-NET
    g. [Organization] CyberVision Co.,Ltd.
    m. [Administrative Contact] YO2225JP
    n. [Technical Contact] YO2225JP
    p. [Nameserver]

    Less Specific Info.
    ----------
    Media Exchange Co., Inc.
    Media EXchange, Inc.
    SUBA-200-C07 [Sub Allocation] 211.13.210.0/24

    More Specific Info.
    ----------
    No match!!

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 4 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.7411862297801741
Message Error
  • Error Line 1, 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 7, Column 56: NET-enabling start-tag requires SHORTTAG YES
    <link rel="stylesheet" href="index.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.

  • Error Line 8, Column 71: document type does not allow element "META" here
    <meta http-equiv="Content-Type" content="text/html; charset=Shift_JIS">

    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 10, 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 11, Column 24: document type does not allow element "BODY" here
    <body bgcolor="#ffffff">

    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 16, Column 33: NET-enabling start-tag requires SHORTTAG YES
    <p class="ageTxt">◆◇ 年齢認証 ◇◆<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 17, Column 28: 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.

  • Warning Line 31, 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.

Visitor Analysis

Daily Visitor
  • 1.283 visits

In Page Analysis