ayaka-tokyo.com - robtex.com
ayaka-tokyo.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1777132446 | ||||||
Same first word
ayaka-tokyo.com |
DNS History
12 records (5 active, 7 former)
●NSdocks04.rzone.de2026-03-21 → 2026-04-25 · 3 obs
● 2026-03-21 17:35:12
● 2026-04-25 15:59:22
○NSns1.raidboxes.net2019-12-18 → 2019-12-18 · 3 obs
○ 2026-03-21 17:35:12
○ 2026-04-25 15:59:22
○NSns2.raidboxes.net2019-12-18 → 2019-12-18 · 3 obs
○ 2026-03-21 17:35:12
○ 2026-04-25 15:59:22
○NSns3.raidboxes.net2019-12-18 → 2019-12-18 · 3 obs
○ 2026-03-21 17:35:12
○ 2026-04-25 15:59:22
○NSns4.raidboxes.net2019-12-18 → 2019-12-18 · 3 obs
○ 2026-03-21 17:35:12
○ 2026-04-25 15:59:22
●NSshades17.rzone.de2026-03-21 → 2026-04-25 · 3 obs
● 2026-03-21 17:35:12
● 2026-04-25 15:59:22
●MXalt1.aspmx.l.google.com2026-03-21 → 2026-04-25 · 3 obs
● 2026-03-21 17:35:12
● 2026-04-25 15:59:22
●MXaspmx.l.google.com2026-03-21 → 2026-04-25 · 3 obs
● 2026-03-21 17:35:12
● 2026-04-25 15:59:22
○MXmxext1.mailbox.org2019-12-18 → 2019-12-18 · 3 obs
○ 2026-03-21 17:35:12
○ 2026-04-25 15:59:22
○MXmxext2.mailbox.org2019-12-18 → 2019-12-18 · 3 obs
○ 2026-03-21 17:35:12
○ 2026-04-25 15:59:22
○MXmxext3.mailbox.org2019-12-18 → 2019-12-18 · 3 obs
○ 2026-03-21 17:35:12
○ 2026-04-25 15:59:22
●A23.227.38.652026-03-21 → 2026-04-25 · 2 obs
● 2026-04-25 15:59:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| ayaka-tokyo.com | docks04.rzone.de, shades17.rzone.de | - |
✅ Authoritative Response
Server:217.160.80.131
NS records: docks04.rzone.de, shades17.rzone.de
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ayaka-tokyo.com (unsigned zone)
⏱️ Timing
Total: 2892ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.227.38.65 |
| NS | 2 | docks04.rzone.de, shades17.rzone.de |
| MX | 2 | alt1.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 10) |
| TXT | 2 | brevo-code:9011d68c410eb9283a2469945c74c, google-site-verification=fhXJtYZWBPIPP6I |
| SOA | 1 | shades17.rzone.de hostmaster.strato-rz.d |
Analysis
IP Addresses
ayaka-tokyo.com resolves to a single IP: 23.227.38.65.
Other host names, for instance everydayephemera.co, dewimaya.com, brython.com, elpuredream.com and tilame.com share IP numbers with ayaka-tokyo.com.
Name Servers
ayaka-tokyo.com has two name servers: docks04.rzone.de and shades17.rzone.de.
ayaka-tokyo.com shares the same name server setup as other domains, for example diffraktometrie.com, fairedeals.de, kabaraettchen.de, chaosorchester.de and elpuerto.de.
ayaka-tokyo.com shares some name servers with other domains, for example spymuseum.world, hausverwalter-freiburg.de, i2e.de, leefstijlcoachharderwijk.nl and diecuxhavener-energiegenossenschaft.de.
these name servers are often used with shades13.rzone.de, docks14.rzone.de, shades15.rzone.de, shades02.rzone.de, docks10.rzone.de, docks12.rzone.de, docks06.rzone.de, docks03.rzone.de, shades05.rzone.de and shades01.rzone.de.
Host names with two IP numbers:
docks04.rzone.de points to: 2001:8d8:fe:53:5747:2a74:d:4 and 217.160.80.131; shades17.rzone.de points to: 2607:f1c0:fe:53:185:132:34:144 and 185.132.34.144.
Mail Servers
ayaka-tokyo.com is served by two mail servers: aspmx.l.google.com and alt1.aspmx.l.google.com.
ayaka-tokyo.com shares the mail server setup with other domains, for example streetstylestore.com, piecasso.com, shsf.org, ranpakcorp.com and debnar.org.
ayaka-tokyo.com shares some mail servers with other domains, at least partially; for instance ns500698.ns500758.ns500758.ns500759.ns500735.ns500698.ns500735.ns500698.ns500736.ns500576.ns500708.ns500652.ns500619.ns500576.trackreceptor.com, ns500754.ns500742.ns500754.ns500671.ns500671.ns500731.ns500705.ns500688.ns500671.ns500649.tenderladiesbz.com, ns500742.ns500671.ns500742.ns500754.ns500754.ns500742.ns500671.ns500705.ns500704.ns500678.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com, ns500698.ns500698.ns500698.ns500759.ns500735.ns500698.ns500698.ns500735.ns500698.ns500576.ns500619.ns500698.ns500686.ns500652.trackreceptor.com and ns500754.ns500754.ns500705.ns500678.ns500671.ns500704.ns500678.ns500291.ns500666.tenderladiesbz.com.
these mail servers are often used together with the mail servers alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to: 2607:f8b0:4023:c06::1a and 142.251.2.27; alt1.aspmx.l.google.com points to: 2800:3f0:4003:c0f::1b and 108.177.123.27.