rumble-records.com - robtex.com
rumble-records.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=1774544192 | ||||||
Subdomains
mail.rumble-records.com |
DNS History
12 records (12 active, 0 former)
●NSdns057.b.register.com2026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 17:18:10
●NSdns1.register.com2026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 17:18:10
●NSdns116.a.register.com2026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 17:18:10
●NSdns176.d.register.com2026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 17:18:10
●NSdns2.register.com2026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 17:18:10
●NSdns244.c.register.com2026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 17:18:10
●MXalt1.aspmx.l.google.com2026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 17:18:10
●MXalt2.aspmx.l.google.com2026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 17:18:10
●MXalt3.aspmx.l.google.com2026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 17:18:10
●MXalt4.aspmx.l.google.com2026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 17:18:10
●MXaspmx.l.google.com2026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 17:18:10
●A199.34.228.782026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 17:18:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| rumble-records.com | dns1.register.com, dns2.register.com | 2 records |
✅ Authoritative Response
Server:162.159.26.197
NS records: dns1.register.com, dns2.register.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for rumble-records.com (unsigned zone)
⏱️ Timing
Total: 189ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 199.34.228.78 |
| NS | 4 | dns057.b.register.com, dns244.c.register.com... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt2.aspmx.l.google.com (pri: 5)... |
| SOA | 1 | dns116.a.register.com root.register.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (dns1.register.com, dns2.register.com)
Analysis
Hierarchy
rumble-records.com is the parent of mail.rumble-records.com.
IP Addresses
rumble-records.com resolves to one IP number: 199.34.228.78.
other host names including caboholics.com, new.railroadpass.com, maletime.org, mail.tennisclub-tiergarten.de and www.gamerizon.com share IP numbers with rumble-records.com.
Name Servers
rumble-records.com is delegated to six name servers: dns1.register.com, dns2.register.com, dns116.a.register.com, dns057.b.register.com, dns244.c.register.com and dns176.d.register.com.
rumble-records.com at least partially shares name servers with other domains, for instance ifindit.com, tucsonspinecenter.com, mercedespartsdelivered.com, polyone.us and grikos.com.
These name servers are commonly used with the following name servers: dns177.d.register.com, dns082.d.register.com, dns083.d.register.com, dns249.d.register.com, dns1.srsplus.com, dns2.srsplus.com, dns216.c.register.com, dns248.c.register.com, dns232.c.register.com and dns234.c.register.com.
Host names with one IP number: Host name dns1.register.com points to 162.159.27.248; Host name dns2.register.com points to 162.159.26.197; Host name dns116.a.register.com points to 216.21.231.116; Host name dns057.b.register.com points to 216.21.232.57; Host name dns244.c.register.com points to 216.21.235.244; Host name dns176.d.register.com points to 216.21.236.176.
Mail Servers
rumble-records.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
rumble-records.com shares some mail servers with other domains, at least partially, for instance ns500698.ns500759.ns500698.ns500759.ns500698.ns500735.ns500736.ns500735.ns500576.ns500576.ns500698.ns500698.ns500619.ns500686.ns500619.ns500576.trackreceptor.com, bakuevents.com, ns500758.ns500698.ns500698.ns500758.ns500759.ns500698.ns500735.ns500735.ns500698.ns500698.ns500698.ns500576.ns500698.ns500708.ns500576.ns500576.ns500576.trackreceptor.com, ns500734.ns500734.ns500699.ns500734.ns500699.ns500699.ns500699.ns500699.ns500699.ns500699.ns500693.ns500699.ns500588.ns500699.ns500602.dtrkdll.com and ns500698.ns500698.ns500759.ns500759.ns500736.ns500698.ns500735.ns500736.ns500736.ns500698.ns500736.ns500708.ns500619.ns500619.trackreceptor.com.
these mail servers are often used with 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.26
alt1.aspmx.l.google.com points to 2800:3f0:4003:c0f::1a and 108.177.123.26
alt2.aspmx.l.google.com points to 2a00:1450:400b:c02::1a and 172.253.116.27
alt3.aspmx.l.google.com points to 2a00:1450:4009:c0f::1b and 192.178.223.26
alt4.aspmx.l.google.com points to 2607:f8b0:4001:c70::1a and 192.178.209.26