zapmeta.jp - robtex.com
zapmeta.jp
| DNSSEC | ⚠️ Not signed | ||||||
| NS | dns01.gmoserver.jp ⚠️ Not in zone NS records | ||||||
| A | 157.7.33.81🇯🇵 GMO-DNS157.7.33.0/24 GMO Internet,inc. Network-Team. | ||||||
| PTR | dns01.gmoserver.jp | ||||||
| NS | dns02.gmoserver.jp ⚠️ Not in zone NS records | ||||||
| A | 157.7.34.81🇯🇵 GMO-DNS157.7.34.0/24 GMO Internet,inc. Network-Team. | ||||||
| PTR | dns02.gmoserver.jp | ||||||
jp
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | z.dns.jp ⭐ | ||||||
| NS | a.dns.jp | ||||||
| NS | b.dns.jp | ||||||
| NS | c.dns.jp | ||||||
| NS | d.dns.jp | ||||||
| NS | e.dns.jp | ||||||
| NS | f.dns.jp | ||||||
| NS | g.dns.jp | ||||||
| NS | h.dns.jp | ||||||
| SOA | z.dns.jproot@dns.jp serial=1778740202 | ||||||
Same first word
Similar names
zetamap.com |
zapmate.com |
zamtape.com |
zapteam.it |
amazept.com |
metazap.nl |
zapteam.dk |
amaztep.com |
amazpet.com |
teamzap.com |
zetamap.it |
zampate.com |
zapteam.com |
metazap.com |
DNS History
8 records (2 active, 6 former)
●NSdns01.gmoserver.jp2026-03-05 → 2026-05-14 · 3 obs
○ 2017-02-15 02:06:18
● 2026-03-05 17:53:34
● 2026-05-14 06:39:56
● 2026-03-05 17:53:34
● 2026-05-14 06:39:56
●NSdns02.gmoserver.jp2026-03-05 → 2026-05-14 · 3 obs
○ 2017-02-15 02:06:18
● 2026-03-05 17:53:34
● 2026-05-14 06:39:56
● 2026-03-05 17:53:34
● 2026-05-14 06:39:56
○NSns1.p30.dynect.net2016-04-22 → 2017-02-15 · 4 obs
● 2016-04-22 02:58:10
● 2017-02-15 02:06:18
○ 2026-03-05 17:53:34
○ 2026-05-14 06:39:56
● 2017-02-15 02:06:18
○ 2026-03-05 17:53:34
○ 2026-05-14 06:39:56
○NSns2.p30.dynect.net2016-04-22 → 2017-02-15 · 4 obs
● 2016-04-22 02:58:10
● 2017-02-15 02:06:18
○ 2026-03-05 17:53:34
○ 2026-05-14 06:39:56
● 2017-02-15 02:06:18
○ 2026-03-05 17:53:34
○ 2026-05-14 06:39:56
○NSns3.p30.dynect.net2016-04-22 → 2017-02-15 · 4 obs
● 2016-04-22 02:58:10
● 2017-02-15 02:06:18
○ 2026-03-05 17:53:34
○ 2026-05-14 06:39:56
● 2017-02-15 02:06:18
○ 2026-03-05 17:53:34
○ 2026-05-14 06:39:56
○NSns4.p30.dynect.net2016-04-22 → 2017-02-15 · 4 obs
● 2016-04-22 02:58:10
● 2017-02-15 02:06:18
○ 2026-03-05 17:53:34
○ 2026-05-14 06:39:56
● 2017-02-15 02:06:18
○ 2026-03-05 17:53:34
○ 2026-05-14 06:39:56
○A94.236.112.1922016-04-22 → 2016-06-24 · 4 obs
● 2016-04-22 02:58:10
● 2016-06-24 17:59:52
○ 2017-02-09 16:04:08
○ 2026-05-14 06:39:56
● 2016-06-24 17:59:52
○ 2017-02-09 16:04:08
○ 2026-05-14 06:39:56
○A94.236.94.02017-02-09 → 2017-02-15 · 5 obs
○ 2016-06-24 17:59:52
● 2017-02-09 16:04:08
● 2017-02-15 02:06:18
○ 2026-03-05 17:53:34
○ 2026-05-14 06:39:56
● 2017-02-09 16:04:08
● 2017-02-15 02:06:18
○ 2026-03-05 17:53:34
○ 2026-05-14 06:39:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | c.dns.jp, e.dns.jp, a.dns.jp, d.dns.jp... | - |
| zapmeta.jp | dns01.gmoserver.jp, dns02.gmoserver.jp | - |
✅ Authoritative Response
Server:157.7.34.81
NS records: dns01.gmoserver.jp, dns02.gmoserver.jp
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for zapmeta.jp (unsigned zone)
⏱️ Timing
Total: 2042ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
zapmeta.jp's delegation uses two name servers, dns01.gmoserver.jp and dns02.gmoserver.jp.
zapmeta.jp shares the same name server setup as other domains, for example osmac.co.jp, hikita.co.jp, hkr-tokyo.com, drivecare.jp and relist.jp.
zapmeta.jp at least partially shares name servers with other domains; for instance to-af.com.
Host names with a single IP:
dns01.gmoserver.jp points to 157.7.33.81.
dns02.gmoserver.jp points to 157.7.34.81.