rootcode.events - dns.ninja
rootcode.events
events
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | v0n0.nic.events ⭐ | ||||||
| NS | v0n1.nic.events | ||||||
| NS | v0n2.nic.events | ||||||
| NS | v0n3.nic.events | ||||||
| NS | v2n0.nic.events | ||||||
| NS | v2n1.nic.events | ||||||
| SOA | v0n0.nic.eventshostmaster@donuts.email serial=1789579613 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
8 records (8 active, 0 former)
●NSdns1.registrar-servers.com2026-09-08 → 2026-09-16 · 2 obs
● 2026-09-16 17:38:18
●NSdns2.registrar-servers.com2026-09-08 → 2026-09-16 · 2 obs
● 2026-09-16 17:38:18
●MXalt1.aspmx.l.google.com2026-09-08 → 2026-09-16 · 2 obs
● 2026-09-16 17:38:18
●MXalt2.aspmx.l.google.com2026-09-08 → 2026-09-16 · 2 obs
● 2026-09-16 17:38:18
●MXaspmx.l.google.com2026-09-08 → 2026-09-16 · 2 obs
● 2026-09-16 17:38:18
●MXaspmx2.googlemail.com2026-09-08 → 2026-09-16 · 2 obs
● 2026-09-16 17:38:18
●MXaspmx3.googlemail.com2026-09-08 → 2026-09-16 · 2 obs
● 2026-09-16 17:38:18
●A192.64.119.2422026-09-08 → 2026-09-16 · 2 obs
● 2026-09-16 17:38:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| events | v0n0.nic.events, v0n1.nic.events, v0n2.nic.events, v0n3.nic.events... | 12 records |
| rootcode.events | dns1.registrar-servers.com, dns2.registrar-servers.com | - |
✅ Authoritative Response
Server:156.154.132.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for rootcode.events (unsigned zone)
⏱️ Timing
Total: 1428ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 192.64.119.242 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | google-site-verification=9VE7_jqvMrQD4iA |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (v0n0.nic.events, v0n1.nic.events, v0n2.nic.events...)
Analysis
IP Addresses
rootcode.events has exactly one IP address — 192.64.119.242.
sports128.org, nexavaluegroup.com, b3d.center plus two other host names have IP numbers in common with rootcode.events.
Name Servers
rootcode.events uses two name servers for its delegation: dns1.registrar-servers.com and dns2.registrar-servers.com.
The name server configuration of rootcode.events is shared with other domains, for instance altadena-adjusters.com, jonable.com, bullbeardevice.com and two others.
rootcode.events has a partial name server overlap with other domains — among them bezelware.com and jxnart.com.
The two host names dns1.registrar-servers.com and dns2.registrar-servers.com each have a pair of IP addresses: dns1.registrar-servers.com has 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com has 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
rootcode.events is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
At least some of the mail servers used by rootcode.events are shared with other domains: team-bumblee.com, fairiesdownunder.com, kaitlynnelliottphotography.com and two others among them.
These mail servers are often deployed together with alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c0b::1b.
alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 192.178.234.27 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.