dc1.jp - robtex.com

dc1.jp

DNSSECπŸ”’ Signed (DS record present)
NSns1.dc1.jp ⭐
A2400:8500:2002:3161:160:251:168:187πŸ‡―πŸ‡΅ GMOOSK-NET2400:8500:2000::/36 GMO Internet,Inc Cerulean Tower, 11F Sakuragaokacho-26-1 Shibuya-ku, Tokyo 150-8512, Japan
PTRv160-251-168-187.m5m8.static.cnode.jp
A160.251.168.187πŸ‡―πŸ‡΅ GMOOSK-NET160.251.168.0/24 GMO Internet,Inc Cerulean Tower, 11F Sakuragaokacho-26-1 Shibuya-ku, Tokyo 150-8512, Japan
PTRv160-251-168-187.m5m8.static.cnode.jp
NSns2.dc1.jp
A2a01:4f8:251:45c:9e78:84d9:aea1:bf90πŸ‡©πŸ‡ͺ Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK
A168.119.140.25πŸ‡©πŸ‡ͺ Hetzner168.119.0.0/16 HETZNER-DC
PTRstatic.25.140.119.168.clients.your-server.de
NSns3.dc1.jp
A2a04:bdc7:100:f511:9e78:84d9:aea1:bf90πŸ‡ΊπŸ‡Έ HOSTHATCH-ASN2a04:bdc7:100::/48 HostHatch LAX
A31.220.30.108πŸ‡ΊπŸ‡Έ HOSTHATCH-ASN31.220.30.0/24 HostHatch LAX
PTRfaith.michiru.top
NSns4.dc1.jp
A2406:ef80:3:7123:9e78:84d9:aea1:bf90πŸ‡ΊπŸ‡Έ HOSTHATCH-ASN2406:ef80:3::/48 HostHatch LLC 100 S. Ashley Drive, Suite 600
A77.90.35.134πŸ‡©πŸ‡ͺ HOSTHATCH-ASN77.90.35.0/24
PTRet1hjvfxhac.canva.com
MXmail.dc1.jp ⭐
A2406:8c00:0:3459:133:18:124:212πŸ‡―πŸ‡΅ KAGOYAJAPAN2406:8c00::/32 KAGOYA Japan Inc.
PTRmail.dc1.jp
A133.18.124.212πŸ‡―πŸ‡΅ KAGOYAJAPAN133.18.0.0/16 KAGOYA Japan Inc.
PTRmail.dc1.jp
TXTv=spf1 mx -all
TXTgoogle-site-verification=BNI2kb6Y7CLXbrrl_crfAxsgl1dtSlp737ftx11FTiA
SOAns1.dc1.jpadmin@dc1.jp 2026-01-04 #20

jp

DNSSECπŸ”’ Signed (DS record present)
NSz.dns.jp ⭐
NSa.dns.jp
NSb.dns.jp
NSc.dns.jp
NSd.dns.jp
NSe.dns.jp
NSf.dns.jp
NSg.dns.jp
NSh.dns.jp
SOAz.dns.jproot@dns.jp serial=1773558003

Subdomains

Same first word

Similar names

DNS History

14 records (5 active, 9 former)

20162017201820192020202120222023202420252026NSns1.dc1.jpns2.dc1.jpns3.dc1.jpns4.dc1.jp01.dnsv.jp02.dnsv.jpMXmail.dc1.jpalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comaspmx4.googlemail.comaspmx5.googlemail.com
β—‹NS01.dnsv.jp2015-07-20 β†’ 2016-02-26 Β· 4 obs
● 2015-07-20 10:42:30
● 2016-02-26 11:54:22
β—‹ 2016-08-19 08:29:36
β—‹ 2026-03-23 14:36:12
β—‹NS02.dnsv.jp2015-07-20 β†’ 2016-02-26 Β· 4 obs
● 2015-07-20 10:42:30
● 2016-02-26 11:54:22
β—‹ 2016-08-19 08:29:36
β—‹ 2026-03-23 14:36:12
●NSns1.dc1.jp2026-03-21 β†’ 2026-03-23 Β· 3 obs
β—‹ 2016-08-19 08:29:36
● 2026-03-21 07:23:12
● 2026-03-23 14:36:12
●NSns2.dc1.jp2026-03-21 β†’ 2026-03-23 Β· 3 obs
β—‹ 2016-08-19 08:29:36
● 2026-03-21 07:23:12
● 2026-03-23 14:36:12
●NSns3.dc1.jp2026-03-21 β†’ 2026-03-23 Β· 3 obs
β—‹ 2016-08-19 08:29:36
● 2026-03-21 07:23:12
● 2026-03-23 14:36:12
●NSns4.dc1.jp2026-03-21 β†’ 2026-03-23 Β· 3 obs
β—‹ 2016-08-19 08:29:36
● 2026-03-21 07:23:12
● 2026-03-23 14:36:12
β—‹MXalt1.aspmx.l.google.com2015-07-20 β†’ 2016-02-26 Β· 4 obs
● 2015-07-20 10:42:30
● 2016-02-26 11:54:22
β—‹ 2016-08-19 08:29:36
β—‹ 2026-03-23 14:36:12
β—‹MXalt2.aspmx.l.google.com2015-07-20 β†’ 2016-02-26 Β· 4 obs
● 2015-07-20 10:42:30
● 2016-02-26 11:54:22
β—‹ 2016-08-19 08:29:36
β—‹ 2026-03-23 14:36:12
β—‹MXaspmx.l.google.com2015-07-20 β†’ 2016-02-26 Β· 4 obs
● 2015-07-20 10:42:30
● 2016-02-26 11:54:22
β—‹ 2016-08-19 08:29:36
β—‹ 2026-03-23 14:36:12
β—‹MXaspmx2.googlemail.com2015-07-20 β†’ 2016-02-26 Β· 4 obs
● 2015-07-20 10:42:30
● 2016-02-26 11:54:22
β—‹ 2016-08-19 08:29:36
β—‹ 2026-03-23 14:36:12
β—‹MXaspmx3.googlemail.com2015-07-20 β†’ 2016-02-26 Β· 4 obs
● 2015-07-20 10:42:30
● 2016-02-26 11:54:22
β—‹ 2016-08-19 08:29:36
β—‹ 2026-03-23 14:36:12
β—‹MXaspmx4.googlemail.com2015-07-20 β†’ 2016-02-26 Β· 4 obs
● 2015-07-20 10:42:30
● 2016-02-26 11:54:22
β—‹ 2016-08-19 08:29:36
β—‹ 2026-03-23 14:36:12
β—‹MXaspmx5.googlemail.com2015-07-20 β†’ 2016-02-26 Β· 4 obs
● 2015-07-20 10:42:30
● 2016-02-26 11:54:22
β—‹ 2016-08-19 08:29:36
β—‹ 2026-03-23 14:36:12
●MXmail.dc1.jp2026-03-21 β†’ 2026-03-23 Β· 3 obs
β—‹ 2016-08-19 08:29:36
● 2026-03-21 07:23:12
● 2026-03-23 14:36:12

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
jpb.dns.jp, d.dns.jp, a.dns.jp, c.dns.jp...-
dc1.jpns4.dc1.jp, ns3.dc1.jp, ns1.dc1.jp, ns2.dc1.jp8 records

βœ… Authoritative Response

Server:160.251.168.187

NS records: ns4.dc1.jp, ns3.dc1.jp, ns1.dc1.jp, ns2.dc1.jp

πŸ”’ DNSSEC Status

πŸ” Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 1029ms | Queries: -

πŸ“„ Records

TypeCountSample Data
NS4ns2.dc1.jp, ns4.dc1.jp...
MX1mail.dc1.jp (pri: 10)
TXT2v=spf1 mx -all, google-site-verification=BNI2kb6Y7CLXbrr
SOA1ns1.dc1.jp admin.dc1.jp

πŸ“Œ Glue Records Collected

Total: 8

In-bailiwick: 8 (ns1.dc1.jp, ns2.dc1.jp, ns3.dc1.jp...)

Analysis

Hierarchy

The parent of ns3.dc1.jp, ns4.dc1.jp, ns2.dc1.jp, mail.dc1.jp and ns1.dc1.jp is dc1.jp.

Name Servers

dc1.jp is delegated to four name servers: ns1.dc1.jp, ns2.dc1.jp, ns3.dc1.jp and ns4.dc1.jp.

dc1.jp shares name servers with other domains at least partially, for instance rin.cat, rincat.ch and alyce.ch.

these name servers are commonly used together with ns1.alyce.ch, ns2.alyce.ch, ns3.alyce.ch and ns4.alyce.ch.

Host names with two IPs: ns1.dc1.jp points to 2400:8500:2002:3161:160:251:168:187 and 160.251.168.187; ns2.dc1.jp points to 2a01:4f8:251:45c:9e78:84d9:aea1:bf90 and 168.119.140.25; ns3.dc1.jp points to 2a04:bdc7:100:f511:9e78:84d9:aea1:bf90 and 31.220.30.108; ns4.dc1.jp points to 2406:ef80:3:7123:9e78:84d9:aea1:bf90 and 77.90.35.134.

Mail Servers

dc1.jp is served by a single mail server, mail.dc1.jp.

dc1.jp shares the same mail server setup as alyce.ch, rin.cat and rincat.ch.

Hostname mail.dc1.jp resolves to two IPs: 2406:8c00:0:3459:133:18:124:212 and 133.18.124.212.