hpcwire.jp
Its Domain Power Rank is relatively low. This domain was registered at least 10 years ago. Links from multiple referring domains appear in the observed data.
- Global Rank
- #3,490,305
▼ 1,637,977
- Rank in TLD
- #72,108
▼ 30,661
- Referring Domains
- 40
▼ 1
- Avg. Referrer Power Rank
- 33.0
- Subdomains
- 4
- Domain age
- 13 yr 8 mo
Link Overview
- Avg. Referrer Power Rank
- 33.0
- Median Referrer Power Rank
- 29.6
- Referring Domains
- 40
- Linked Domains
- 747
Referring Domains by Power Rank
0–9 5
10–19 5
20–29 11
30–39 8
40–49 5
50–59 1
60–69 3
70–79 0
80–89 1
90–100 1
Total 40
Referring Domains
| Referring domain | Power Rank | Global Rank |
|---|---|---|
| wikipedia.org | 91.8 | #34 |
| hatena.ne.jp | 82.7 | #270 |
| cocolog-nifty.com | 66.1 | #6,323 |
| riken.jp | 62.0 | #12,225 |
| icm.edu.pl | 61.3 | #13,852 |
| kit.ac.jp | 50.7 | #86,195 |
| academist-cf.com | 47.7 | #141,189 |
| jsiam.org | 43.4 | #288,715 |
| exa-corp.co.jp | 41.3 | #397,405 |
| shudo.net | 40.6 | #441,630 |
Basic Information
- TLD
- .jpJapan
- Registration date
- 5 Mar 2013
- Last updated
- 31 Mar 2026
- Expires
- 31 Mar 2027 (146 days remaining)
- Domain statuses
- Active
- Registry
- Japan Registry Services Co., Ltd.
Subdomain
adserver.hpcwire.jpwihpc.hpcwire.jpwww.hpcwire.jpwww4.hpcwire.jp
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | hpcwire.jp | 600 | 160.16.104.8 |
| MX | hpcwire.jp | 600 | 10 dmail.hpcwire.jp |
| NS | hpcwire.jp | 600 | ns0.kagoya.net |
| NS | hpcwire.jp | 600 | ns1.kagoya.net |
| SOA | hpcwire.jp | 600 | ns.kagoya.net. root.kagoya.net. 2026030001 4200 300 3600000 600 |
| TXT | hpcwire.jp | 600 | v=spf1 include:kagoya.net ~all |
Email Authentication
- MX
- Valid
- SPF
- Valid
- DMARC
- Warning
DMARC is set to p=none, which does not ask receiving servers to quarantine or reject failing messages.
Some information is cached or comes from our own analysis, so it may not be current or complete. Our link analysis does not cover every link on the web. Metrics are based on our own methodology and should not be taken as definitive assessments of a domain’s or service’s quality or trustworthiness.