eisbahn.jp - robtex.com
eisbahn.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=1785163502 | ||||||
Subdomains
www.eisbahn.jp |
Same first word
Similar names
DNS History
20 records (10 active, 10 former)
○NSns-1275.awsdns-31.org2017-03-17 → 2017-03-17 · 4 obs
● 2017-03-17 23:15:40
○ 2026-04-03 10:11:02
○ 2026-07-27 14:49:52
○NSns-1584.awsdns-06.co.uk2017-03-17 → 2017-03-17 · 4 obs
● 2017-03-17 23:15:40
○ 2026-04-03 10:11:02
○ 2026-07-27 14:49:52
○NSns-26.awsdns-03.com2017-03-17 → 2017-03-17 · 4 obs
● 2017-03-17 23:15:40
○ 2026-04-03 10:11:02
○ 2026-07-27 14:49:52
○NSns-870.awsdns-44.net2017-03-17 → 2017-03-17 · 4 obs
● 2017-03-17 23:15:40
○ 2026-04-03 10:11:02
○ 2026-07-27 14:49:52
●NSns-cloud-e1.googledomains.com2026-04-03 → 2026-07-27 · 3 obs
● 2026-04-03 10:11:02
● 2026-07-27 14:49:52
●NSns-cloud-e2.googledomains.com2026-04-03 → 2026-07-27 · 3 obs
● 2026-04-03 10:11:02
● 2026-07-27 14:49:52
●NSns-cloud-e3.googledomains.com2026-04-03 → 2026-07-27 · 3 obs
● 2026-04-03 10:11:02
● 2026-07-27 14:49:52
●NSns-cloud-e4.googledomains.com2026-04-03 → 2026-07-27 · 3 obs
● 2026-04-03 10:11:02
● 2026-07-27 14:49:52
○NSns0.xname.org2015-05-11 → 2015-05-11 · 3 obs
○ 2015-10-20 00:14:54
○ 2026-07-27 14:49:52
○NSns01.eisbahn.jp2015-05-11 → 2016-07-12 · 4 obs
● 2016-07-12 21:55:00
○ 2017-03-17 23:15:40
○ 2026-07-27 14:49:52
○NSns1.maihama-net.com2015-10-20 → 2016-07-12 · 5 obs
● 2015-10-20 00:14:54
● 2016-07-12 21:55:00
○ 2017-03-17 23:15:40
○ 2026-07-27 14:49:52
○NSns1.xname.org2015-05-11 → 2015-05-11 · 3 obs
○ 2015-10-20 00:14:54
○ 2026-07-27 14:49:52
○NSns3.maihama-net.com2015-10-20 → 2016-07-12 · 5 obs
● 2015-10-20 00:14:54
● 2016-07-12 21:55:00
○ 2017-03-17 23:15:40
○ 2026-07-27 14:49:52
●MXalt1.aspmx.l.google.com2017-03-17 → 2026-07-27 · 3 obs
● 2017-03-17 23:15:40
● 2026-07-27 14:49:52
●MXalt2.aspmx.l.google.com2017-03-17 → 2026-07-27 · 3 obs
● 2017-03-17 23:15:40
● 2026-07-27 14:49:52
●MXalt3.aspmx.l.google.com2017-03-17 → 2026-07-27 · 3 obs
● 2017-03-17 23:15:40
● 2026-07-27 14:49:52
●MXalt4.aspmx.l.google.com2017-03-17 → 2026-07-27 · 3 obs
● 2017-03-17 23:15:40
● 2026-07-27 14:49:52
●MXaspmx.l.google.com2017-03-17 → 2026-07-27 · 3 obs
● 2017-03-17 23:15:40
● 2026-07-27 14:49:52
○MXsmtp.eisbahn.jp2015-05-11 → 2016-07-12 · 4 obs
● 2016-07-12 21:55:00
○ 2017-03-17 23:15:40
○ 2026-07-27 14:49:52
●A199.36.158.1002026-04-03 → 2026-07-27 · 2 obs
● 2026-07-27 14:49:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp... | - |
| eisbahn.jp | ns-cloud-e2.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e4.googledomains.com, ns-cloud-e3.googledomains.com | - |
✅ Authoritative Response
Server:216.239.36.110
NS records: ns-cloud-e2.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e4.googledomains.com, ns-cloud-e3.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for eisbahn.jp (unsigned zone)
⏱️ Timing
Total: 775ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 199.36.158.100 |
| NS | 4 | ns-cloud-e3.googledomains.com, ns-cloud-e2.googledomains.com... |
| MX | 5 | alt3.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 1)... |
| TXT | 2 | google-site-verification=dXfMVcL5_0_ma_F, hosting-site=eisbahn |
| SOA | 1 | ns-cloud-e1.googledomains.com cloud-dns- |
Analysis
Hierarchy
www.eisbahn.jp is delegated beneath eisbahn.jp.
IP Addresses
eisbahn.jp has exactly one IP address — 199.36.158.100.
foniclinicainfantil.com.br, account-fb-transparent-aed02.firebaseapp.com, caseforpage1000349649594.web.app plus two other host names have IP numbers in common with eisbahn.jp.
Name Servers
Four name servers handle the delegation for eisbahn.jp: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.
There is at least partial name server overlap between eisbahn.jp and other domains — mirakie.com, runwalkwithpride.org, viajeselbuenfin.com and two more among them.
All four hostnames — ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com — resolve to two IP numbers apiece: ns-cloud-e1.googledomains.com to 216.239.32.110 and 2001:4860:4802:32::6e; ns-cloud-e2.googledomains.com to 216.239.34.110 and 2001:4860:4802:34::6e; ns-cloud-e3.googledomains.com to 216.239.36.110 and 2001:4860:4802:36::6e; ns-cloud-e4.googledomains.com to 216.239.38.110 and 2001:4860:4802:38::6e.
Mail Servers
Five mail servers handle eisbahn.jp: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by eisbahn.jp are shared with other domains: ns500754.ns500742.ns500754.ns500731.ns500704.ns500704.ns500731.ns500705.ns500705.ns500678.ns500291.ns500291.ns500666.tenderladiesbz.com, ns500754.ns500742.ns500742.ns500742.ns500671.ns500731.ns500704.ns500678.ns500705.ns500688.ns500671.ns500666.tenderladiesbz.com, ns500759.ns500758.ns500698.ns500759.ns500758.ns500735.ns500735.ns500698.ns500735.ns500708.ns500698.ns500698.ns500619.ns500686.ns500619.ns500576.trackreceptor.com and two others among them.
These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx.l.google.com has two IP addresses: 172.253.63.27 and 2607:f8b0:4004:c29::1b.
alt1.aspmx.l.google.com has two IP addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com has two IP addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com has two IP addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com has two IP addresses: 172.253.157.26 and 2a00:1450:400c:c23::1a.