Please select GA View:

Japanpost.Jp - Info

japanpost.jp receives about 1,252,402 unique visitors and 5,009,607 (4.00 per visitor) page views per day which should earn about $16,107.39/day from advertising revenue. Estimated site value is $8,605,775.41. According to Alexa Traffic Rank japanpost.jp is ranked number 684 in the world and 0.0889% of global Internet users visit it. Site is hosted in Nishinomiya, 13, 662-0934, Japan and links to network IP address 203.202.223.140. This server supports HTTPS and doesn't support HTTP/2.

About - japanpost.jp

Guide to Japanese postal services, saving system, and life insurance. With organization, full description of services, history, and management goals.
日本郵政株式会社のWebサイトへようこそ。日本郵政株式会社は、日本郵便株式会社・株式会社ゆうちょ銀行・株式会社かんぽ生命保険などからなる日本郵政グループの持株会社です。

How did japanpost.jp look in the past? Edit Site Info

japanpost.jp Profile

Title: 日本郵政ホーム‐日本郵政
Description: Guide to Japanese postal services, saving system, and life insurance. With organization, full description of services, history, and management goals.
Keywords: 日本郵政,日本郵政グループ,ＪＰグループ,JPグループ,JAPANPOST,民営化,郵政民営化,ゆうせい,郵政公社

Last update was 161 days ago

This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with japanpost.jp in any way. Only publicly available statistics data are displayed.

How popular is japanpost.jp?

1.3M daily visitors

Daily Unique Visitors:: 1,252,402
Monthly Unique Visitors:: 37,572,060
Pages per Visit:: 4.00
Daily Pageviews:: 5,009,607
Alexa Rank:: 684 visit alexa
Alexa Reach:: 0.0889% (of global internet users)
Avg. visit duration:: 06:45
Bounce rate:: 34.73%

*All traffic values are estimates only.

Traffic sources

Direct:: 45.31%
Referral:: 10.84%
Search:: 43.40%
Social:: 0.46%
Paid:: 0%

Visitors by country

: Users%Pageviews%Rank
: Japan 94.2%97.1%45
: China 2.1%0.9%5166
: United States 1.4%0.7%11148

Competitive Data

Domain:: japanpost.jp
Rank: (Rank based on keywords, cost and organic traffic): 35,970
Organic Keywords: (Number of keywords in top 20 Google SERP): 24,109
Organic Traffic: (Number of visitors coming from top 20 search results): 41,340
Organic Cost: ((How much need to spend if get same number of visitors from Google Adwords): $7,896.00
Adwords Keywords: (Keywords a website is buying in Google AdWords for ads that appear in paid search results): 0
Adwords Traffic: (Number of visitors brought to the website via paid search results): 0
Adwords Cost: (Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation): $0.00

Full SEMrush Report >>

Data

Domain Authority:: 91
Page Authority:: 57
MozRank:: 6

Backlinks Report

Total Sites Linking In (Alexa):: 18,658
Total Backlinks:: 5,155,987
Follow Links:: 2,510,572
Nofollow Links:: 2,645,415
Referring Domains:: 48,759
Referring IPs:: 29,018
Score:: 61
Trust Score:: 64

Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:: japanpost.jp
Region: (The Ad Standard region to which this site has been assigned.): Pending
Ad filtering: (Chrome is not filtering ads on your site.): Off
Status: (The status of the site that is reviewed for the Better Ads Standards.): Not reviewed

Mobile summary

Region: (The Ad Standard region to which this site has been assigned.): Pending
Ad filtering: (Chrome is not filtering ads on your site.): Off
Status: (The status of the site that is reviewed for the Better Ads Standards.): Not reviewed

Abusive Experience Report

Root domain:: japanpost.jp
Enforcement: (Chrome is not preventing your site from opening new windows or tabs.): Off
Status: (The status of the site reviewed for the abusive experiences.): Not reviewed

How much japanpost.jp can earn?

Daily Revenue:: $16,107.39
Monthly Revenue:: $483,221.70
Yearly Revenue:: $5,879,197.35

*All earnings values are estimates only.

Daily earning by country

: PageviewsEarning
: Japan 4,864,328$15,565.85
: United States 35,067$402.22
: China 45,086$139.32

How much money do japanpost.jp lose due to Adblock?

Daily Revenue Loss:: $557.49
Monthly Revenue Loss:: $16,724.60
Yearly Revenue Loss:: $203,482.61
Daily Pageviews Blocked:: 158,103
Monthly Pageviews Blocked:: 4,743,096
Yearly Pageviews Blocked:: 57,707,667

*All earnings values are estimates only.

Daily revenue loss by country

: BlockedLost Money
: Japan 145,930$466.98
: United States 6,312$72.40
: China 5,861$18.11

How much is japanpost.jp worth?

Website Value:: $8,605,775.41

Where is japanpost.jp hosted?

Server IP:: 203.202.223.140
ASN:: AS7524
ISP:: ITEC HANKYU HANSHIN CO.,LTD.
Server Location:: Nishinomiya
13
662-0934
Japan

Other sites hosted on 203.202.223.140

There are no other sites hosted on this IP

How fast does japanpost.jp load?

Average Load Time:: (654 ms) 92 % of sites are slower

Page Speed (Google PageSpeed Insights)

Suggestions Summary

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 866.8KiB (56% reduction).

Compressing http://www.japanpost.jp/cmn/images/index_visual_18.jpg could save 406.8KiB (73% reduction).
Compressing http://www.japanpost.jp/cmn/images/index_visual_02_r.jpg could save 170.4KiB (46% reduction).
Compressing http://www.japanpost.jp/cmn/images/index_visual_16.jpg could save 152.1KiB (47% reduction).
Compressing http://www.japanpost.jp/assets_c/2017/01/index_bnr_20170118-thumb-215xauto-68573.jpg could save 13.7KiB (***% reduction).
Compressing http://www.japanpost.jp/images/9e5fc7f2dd66ef13148d3b08e6e32e42.jpg could save 11.7KiB (64% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_fb.jpg could save 7.3KiB (64% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_sp_off_guidance.jpg could save 7.1KiB (49% reduction).
Compressing http://www.japanpost.jp/assets_c/2015/01/index_bnr_07-thumb-215xauto-6.jpg could save 5.8KiB (43% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_sp_off_vision.jpg could save 5.8KiB (46% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_sp_off_summary.jpg could save 5.2KiB (46% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_sp_jplife.jpg could save 4.9KiB (45% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_sp_off_presentation.jpg could save 4.8KiB (47% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_sp_off_meeting.jpg could save 4.7KiB (49% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_sp_jpbank.jpg could save 4.7KiB (49% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_sp_jph.jpg could save 4.6KiB (44% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_sp_off_history.jpg could save 4.5KiB (45% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_sp_off_twitter_large.jpg could save 4KiB (35% reduction).
Compressing http://www.japanpost.jp/cmn/images/h_footer_sp.png could save 4KiB (55% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_youtube.jpg could save 3.9KiB (50% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_small_twitter.jpg could save 3.2KiB (37% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_sp_off_hospital.jpg could save 3.2KiB (32% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_sp_off_kanpo.jpg could save 3KiB (34% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_sp_off_post_office.jpg could save 2.4KiB (37% reduction).
Compressing http://www.japanpost.jp/assets_c/2015/01/index_bnr_10-thumb-215xauto-2.jpg could save 2.3KiB (41% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_sp_off_zip_code_search.jpg could save 2.3KiB (32% reduction).
Compressing http://www.japanpost.jp/cmn/images/icon_attention.jpg could save 1.4KiB (71% reduction).
Compressing http://www.japanpost.jp/cmn/images/controls.png could save 1.4KiB (50% reduction).
Compressing http://www.japanpost.jp/cmn/images/icon_sp_twitter.png could save 1.2KiB (50% reduction).
Compressing http://www.japanpost.jp/cmn/images/icon_twitter.png could save 1.2KiB (53% reduction).
Compressing http://www.japanpost.jp/cmn/images/icon_sp_youtube.png could save 1.2KiB (25% reduction).
Compressing http://www.japanpost.jp/cmn/images/h_footer.gif could save 1.1KiB (43% reduction).
Compressing http://www.japanpost.jp/cmn/images/btn_n_textmedium.gif could save 1.1KiB (87% reduction).
Compressing http://www.japanpost.jp/cmn/images/icon_link_01.gif could save 1.1KiB (76% reduction).
Compressing http://www.japanpost.jp/cmn/images/btn_n_textsmall.gif could save 1KiB (80% reduction).
Compressing http://www.japanpost.jp/cmn/images/btn_n_textbig.gif could save 1KiB (80% reduction).
Compressing http://www.japanpost.jp/cmn/images/icon_youtube.png could save 1KiB (30% reduction).
Compressing http://www.japanpost.jp/cmn/images/seach.jpg could save 1KiB (73% reduction).
Compressing http://www.japanpost.jp/cmn/images/arrow_right.gif could save 1KiB (87% reduction).
Compressing http://www.japanpost.jp/cmn/images/btn_n_textsmall_on.gif could save 1KiB (79% reduction).
Compressing http://www.japanpost.jp/cmn/images/icon_fb.png could save 1KiB (50% reduction).
Compressing http://www.japanpost.jp/cmn/images/icon_sp_fb.png could save 1,017B (46% reduction).
Compressing http://www.japanpost.jp/cmn/images/mark_target_blank.jpg could save 967B (72% reduction).
Compressing https://pbs.twimg.com/profile_images/800927881085865984/bCobwisV_bigger.jpg could save 962B (33% reduction).
Compressing http://www.japanpost.jp/cmn/images/icon_sp_nav_arrow_black.png could save 947B (81% reduction).
Compressing http://www.japanpost.jp/cmn/images/h_footermenu.gif could save 907B (58% reduction).
Compressing http://www.japanpost.jp/cmn/images/copyright.gif could save 863B (42% reduction).
Compressing http://www.japanpost.jp/cmn/images/icon_sp_nav_arrow_white.png could save 859B (79% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_footer_jpbank.gif could save 599B (12% reduction).
Compressing http://www.japanpost.jp/cmn/images/bnr_footer_jplife.gif could save 515B (11% reduction).

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://www.japanpost.jp/assets_c/2015/01/index_bnr_07-thumb-215xauto-6.jpg (5 minutes)
http://www.japanpost.jp/assets_c/2015/01/index_bnr_10-thumb-215xauto-2.jpg (5 minutes)
http://www.japanpost.jp/assets_c/2017/01/index_bnr_20170118-thumb-215xauto-68573.jpg (5 minutes)
http://www.japanpost.jp/cmn/css/common.css (5 minutes)
http://www.japanpost.jp/cmn/css/drawer.css (5 minutes)
http://www.japanpost.jp/cmn/css/footer.css (5 minutes)
http://www.japanpost.jp/cmn/css/header.css (5 minutes)
http://www.japanpost.jp/cmn/css/mobile.css (5 minutes)
http://www.japanpost.jp/cmn/css/print-l.css (5 minutes)
http://www.japanpost.jp/cmn/css/reset.css (5 minutes)
http://www.japanpost.jp/cmn/css/slider.css (5 minutes)
http://www.japanpost.jp/cmn/css/style-l.css (5 minutes)
http://www.japanpost.jp/cmn/css/twitter.css (5 minutes)
http://www.japanpost.jp/cmn/images/arrow_right.gif (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_fb.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_footer_japanpost.gif (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_footer_jpbank.gif (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_footer_jplife.gif (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_small_twitter.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_sp_jpbank.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_sp_jph.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_sp_jplife.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_sp_off_guidance.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_sp_off_history.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_sp_off_hospital.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_sp_off_kanpo.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_sp_off_meeting.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_sp_off_post_office.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_sp_off_presentation.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_sp_off_summary.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_sp_off_twitter_large.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_sp_off_vision.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_sp_off_zip_code_search.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/bnr_youtube.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/btn_n_textbig.gif (5 minutes)
http://www.japanpost.jp/cmn/images/btn_n_textmedium.gif (5 minutes)
http://www.japanpost.jp/cmn/images/btn_n_textsmall.gif (5 minutes)
http://www.japanpost.jp/cmn/images/btn_n_textsmall_on.gif (5 minutes)
http://www.japanpost.jp/cmn/images/bx_loader.gif (5 minutes)
http://www.japanpost.jp/cmn/images/controls.png (5 minutes)
http://www.japanpost.jp/cmn/images/copyright.gif (5 minutes)
http://www.japanpost.jp/cmn/images/description.gif (5 minutes)
http://www.japanpost.jp/cmn/images/h_footer.gif (5 minutes)
http://www.japanpost.jp/cmn/images/h_footer_sp.png (5 minutes)
http://www.japanpost.jp/cmn/images/h_footermenu.gif (5 minutes)
http://www.japanpost.jp/cmn/images/icon_attention.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/icon_fb.png (5 minutes)
http://www.japanpost.jp/cmn/images/icon_link_01.gif (5 minutes)
http://www.japanpost.jp/cmn/images/icon_sp_fb.png (5 minutes)
http://www.japanpost.jp/cmn/images/icon_sp_nav_arrow_black.png (5 minutes)
http://www.japanpost.jp/cmn/images/icon_sp_nav_arrow_white.png (5 minutes)
http://www.japanpost.jp/cmn/images/icon_sp_twitter.png (5 minutes)
http://www.japanpost.jp/cmn/images/icon_sp_youtube.png (5 minutes)
http://www.japanpost.jp/cmn/images/icon_twitter.png (5 minutes)
http://www.japanpost.jp/cmn/images/icon_youtube.png (5 minutes)
http://www.japanpost.jp/cmn/images/index_visual_02_r.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/index_visual_16.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/index_visual_18.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/logo.gif (5 minutes)
http://www.japanpost.jp/cmn/images/mark_target_blank.jpg (5 minutes)
http://www.japanpost.jp/cmn/images/seach.jpg (5 minutes)
http://www.japanpost.jp/cmn/js/jquery.js (5 minutes)
http://www.japanpost.jp/cmn/js/plugins.js (5 minutes)
http://www.japanpost.jp/cmn/js/scripts.js (5 minutes)
http://www.japanpost.jp/common/images/share_ico_07.gif (5 minutes)
http://www.japanpost.jp/images/9e5fc7f2dd66ef13148d3b08e6e32e42.jpg (5 minutes)
http://www.japanpost.jp/js/top.js (5 minutes)

https://cdn.syndication.twimg.com/timeline/profile?callback=__twttr.callbacks.tl_i0_profile_JapanPostHD_PR_old&dnt=false&domain=www.japanpost.jp&lang=ja&screen_name=JapanPostHD_PR&suppress_response_codes=true&t=1654321&with_replies=false

(5 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
http://www.google-***ytics.com/***ytics.js (2 hours)
http://c.nakanohito.jp/b3/bi.js (3 hours)

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 9 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:

http://www.japanpost.jp/cmn/js/jquery.js
http://www.japanpost.jp/cmn/js/plugins.js
http://www.japanpost.jp/cmn/js/scripts.js
http://www.japanpost.jp/js/top.js
Optimize CSS Delivery of the following:

http://www.japanpost.jp/cmn/css/reset.css
http://www.japanpost.jp/cmn/css/common.css
http://www.japanpost.jp/cmn/css/header.css
http://www.japanpost.jp/cmn/css/footer.css
http://www.japanpost.jp/cmn/css/style-l.css
http://www.japanpost.jp/cmn/css/slider.css
http://www.japanpost.jp/cmn/css/twitter.css
http://www.japanpost.jp/cmn/css/mobile.css
http://www.japanpost.jp/cmn/css/drawer.css

Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 41% of the final above-the-fold content could be rendered with the full HTML response .

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 3.4KiB (23% reduction).

Minifying http://www.japanpost.jp/cmn/css/print-l.css could save 1.1KiB (22% reduction) after compression.
Minifying http://www.japanpost.jp/cmn/css/mobile.css could save 1,014B (23% reduction) after compression.
Minifying http://www.japanpost.jp/cmn/css/drawer.css could save 810B (30% reduction) after compression.
Minifying http://www.japanpost.jp/cmn/css/style-l.css could save 534B (20% reduction) after compression.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 1.3KiB (30% reduction).

Minifying http://www.japanpost.jp/cmn/js/scripts.js could save 1.3KiB (30% reduction) after compression.

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 1.1KiB (12% reduction).

Minifying http://www.japanpost.jp/ could save 1.1KiB (12% reduction) after compression.

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://www.pos…ai/index2.html">平成28年（2016年）熊本地震の影響について</a> and 1 others are close to other tap targets.
The tap target <a href="http://www.jp-…oto_index.html">熊本県内におけるATMの稼働状況について</a> is close to 1 other tap targets.

Size content to viewport

The contents of your page fit within the viewport. Learn more about sizing content to the viewport.

Use legible font sizes

The text on your page is legible. Learn more about using legible font sizes.

Avoid plugins

Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.

Configure the viewport

Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.

Reduce server response time

Your server responded quickly. Learn more about server response time optimization.

Enable compression

You have compression enabled. Learn more about enabling compression.

Avoid landing page redirects

Your page has no redirects. Learn more about avoiding landing page redirects.

Download optimized image, JavaScript, and CSS resources for this page.

Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:: 90
Vendor reliability:: 90
Privacy:: 90
Child safety:: 95

SSL Checker - SSL Certificate Verify

japanpost.jp supports HTTPS

Verifying SSL Support. Please wait...

Common Name: *.japanpost.jp
Organization:
Location:
Issuer: Cybertrust Japan Public CA G3
Valid from: Mar 8 03:01:42 2018 GMT
Valid until: Mar 22 14:59:00 2019 GMT
Authority:
Keysize:

Verify HTTP/2 Support

japanpost.jp does not support HTTP/2

Verifying HTTP/2.0 Support. Please wait...

Http Header

HTTP/1.0 301 Moved Permanently
Server: Apache
Location: https://www.japanpost.jp/
Cache-Control: max-age=300
Content-Type: text/html; ch***t=iso-8859-1
Age: 173
Date: Sun, 09 Sep 2018 05:03:54 GMT
Expires: Sun, 09 Sep 2018 05:06:01 GMT
Content-Length: 233
Connection: close
HTTP/1.1 200 OK
Date: Sun, 09 Sep 2018 05:03:54 GMT
Content-Type: text/html
Content-Length: 42077
Connection: close
Server: Apache
Accept-Ranges: bytes
Cache-Control: max-age=300
Age: 257
Expires: Sun, 09 Sep 2018 05:04:37 GMT

DNS Lookup

Type	Ip	Target	TTL
TXT			600
SOA			3600
	Mname	ns01.jp-it.net
	Rname	postmaster.ns01.jp-it.net
	Serial Number	2018082901
	Refresh	3600
	Retry	900
	Expire	604800
	Minimum TTL	0
NS		ns01.vips.ne.jp	3600
NS		ns00.vips.ne.jp	3600
NS		ns01.jp-it.net	3600

Whois Lookup

Domain Created:: 0000-00-00
Domain Age:
WhoIs:

whois lookup at whois.jprs.jp...
[ 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 ***/e'.                 ]



Domain Information: [ドメイン情報]

[Domain Name]                   JAPANPOST.JP



[登録者名]                      日本郵政株式会社

[Registrant]                    Japan Post Holdings Co., Ltd.



[Name Server]                   ns01.jp-it.net

[Name Server]                   ns00.vips.ne.jp

[Name Server]                   ns01.vips.ne.jp

[Signing Key]                   



[登録年月日]                    2003/05/28

[有効期限]                      2019/05/31

[状態]                          Active

[最終更新]                      2018/06/01 01:05:08 (JST)



Contact Information: [公開連絡窓口]

[名前]                          藤本　賀一

[Name]                          Fujimoto Norikazu

[Email]                         

[Web Page]                       

[郵便番号]                      100-8798

[住所]                          東京都千代田区霞が関一丁目3番2号

[Postal Address]                1-3-2 Kasumigaseki,

                                Chiyoda-ku,

                                Tokyo 100-8798, Japan

[電話番号]                      03-3504-4320

[FAX番号]                       03-3501-0132