rrserver.com - dns.ninja
rrserver.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=1780873866 | ||||||
Same first word
rrserver.com |
Similar names
DNS History
16 records (9 active, 7 former)
●NSns-cloud-a1.googledomains.com2026-06-07 → 2026-06-07 · 2 obs
● 2026-06-07 23:36:28
●NSns-cloud-a2.googledomains.com2026-06-07 → 2026-06-07 · 2 obs
● 2026-06-07 23:36:28
●NSns-cloud-a3.googledomains.com2026-06-07 → 2026-06-07 · 2 obs
● 2026-06-07 23:36:28
●NSns-cloud-a4.googledomains.com2026-06-07 → 2026-06-07 · 2 obs
● 2026-06-07 23:36:28
○NSns1.mydyndns.org2015-08-09 → 2016-03-10 · 3 obs
● 2016-03-10 17:34:50
○ 2026-06-07 23:36:28
○NSns1189.dns.dyn.com2015-08-09 → 2016-03-10 · 3 obs
● 2016-03-10 17:34:50
○ 2026-06-07 23:36:28
○NSns2154.dns.dyn.com2015-08-09 → 2016-03-10 · 3 obs
● 2016-03-10 17:34:50
○ 2026-06-07 23:36:28
○NSns3144.dns.dyn.com2015-08-09 → 2016-03-10 · 3 obs
● 2016-03-10 17:34:50
○ 2026-06-07 23:36:28
○NSns4195.dns.dyn.com2015-08-09 → 2016-03-10 · 3 obs
● 2016-03-10 17:34:50
○ 2026-06-07 23:36:28
●MXalt1.aspmx.l.google.com2026-06-07 → 2026-06-07 · 1 obs
●MXalt2.aspmx.l.google.com2026-06-07 → 2026-06-07 · 1 obs
●MXalt3.aspmx.l.google.com2026-06-07 → 2026-06-07 · 1 obs
●MXalt4.aspmx.l.google.com2026-06-07 → 2026-06-07 · 1 obs
●MXaspmx.l.google.com2026-06-07 → 2026-06-07 · 1 obs
○A104.137.74.2462015-08-09 → 2015-11-28 · 4 obs
● 2015-11-28 19:35:38
○ 2016-03-10 17:34:50
○ 2026-06-07 23:36:28
○A104.137.76.1442016-03-10 → 2016-03-10 · 3 obs
● 2016-03-10 17:34:50
○ 2026-06-07 23:36:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| rrserver.com | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.36.106
NS records: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 399ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-cloud-a4.googledomains.com, ns-cloud-a3.googledomains.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt4.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns-cloud-a1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-a1.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com...)
Analysis
Name Servers
rrserver.com is served by 4 authoritative name servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.
At least some of rrserver.com's name servers are shared with other domains, for example modavik.com, mayaporrino.com, linkiwork.com and two more.
Four hostnames, each resolving to a pair of IP addresses: ns-cloud-a1.googledomains.com directs to 216.239.32.106 and 2001:4860:4802:32::6a; ns-cloud-a2.googledomains.com directs to 216.239.34.106 and 2001:4860:4802:34::6a; ns-cloud-a3.googledomains.com directs to 216.239.36.106 and 2001:4860:4802:36::6a; ns-cloud-a4.googledomains.com directs to 216.239.38.106 and 2001:4860:4802:38::6a.
Mail Servers
rrserver.com uses 5 mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com plus two additional ones.
rrserver.com shares at least some of its mail servers with other domains — for example ns500731.ns500731.ns500671.ns500754.ns500705.ns500688.ns500688.ns500671.ns500291.ns500678.ns500666.ns500153.tenderladiesbz.com, ns500724.ns500737.ns500724.ns500737.ns500737.ns500724.ns500737.ns500599.ns500682.ns500669.ns500599.ns500631.www.yummyflingsfinder.com, ns500698.ns500698.ns500759.ns500698.ns500735.ns500736.ns500698.ns500698.ns500698.ns500736.ns500698.ns500708.ns500576.ns500619.ns500686.ns500619.ns500576.trackreceptor.com and two more.
These mail servers tend to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and three additional mail servers.
Hosts with two IP numbers each:
aspmx.l.google.com directs traffic to 142.251.167.26 and 2607:f8b0:4004:c23::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 173.194.76.26 and 2a00:1450:400c:c00::1a.