richdoes.com - dns.ninja
richdoes.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=1785366552 | ||||||
Same first word
richdoes.com |
Similar names
DNS History
9 records (8 active, 1 former)
●NSns21.domaincontrol.com2015-08-08 → 2026-07-29 · 2 obs
● 2026-07-29 23:26:58
●NSns22.domaincontrol.com2015-08-08 → 2026-07-29 · 2 obs
● 2026-07-29 23:26:58
●MXalt1.aspmx.l.google.com2015-08-08 → 2026-07-29 · 2 obs
● 2026-07-29 23:26:58
●MXalt2.aspmx.l.google.com2015-08-08 → 2026-07-29 · 2 obs
● 2026-07-29 23:26:58
●MXaspmx.l.google.com2015-08-08 → 2026-07-29 · 2 obs
● 2026-07-29 23:26:58
●MXaspmx2.googlemail.com2015-08-08 → 2026-07-29 · 2 obs
● 2026-07-29 23:26:58
●MXaspmx3.googlemail.com2015-08-08 → 2026-07-29 · 2 obs
● 2026-07-29 23:26:58
●A216.69.141.672026-03-24 → 2026-07-29 · 3 obs
● 2026-03-24 19:29:34
● 2026-07-29 23:26:58
○A97.74.42.792015-08-08 → 2017-05-18 · 4 obs
● 2017-05-18 12:38:46
○ 2026-03-24 19:29:34
○ 2026-07-29 23:26:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| richdoes.com | ns21.domaincontrol.com, ns22.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.100.11
NS records: ns21.domaincontrol.com, ns22.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for richdoes.com (unsigned zone)
⏱️ Timing
Total: 168ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 216.69.141.67 |
| NS | 2 | ns21.domaincontrol.com, ns22.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | NETORGFT11448948.onmicrosoft.com, google-site-verification=GwoIBGSJk5ATTIA |
| SOA | 1 | ns21.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns21.domaincontrol.com, ns21.domaincontrol.com, ns22.domaincontrol.com...)
Analysis
IP Addresses
richdoes.com has exactly one IP address — 216.69.141.67.
metagenx.com, recompany.us, myondokal.com plus two other host names have IP numbers in common with richdoes.com.
Name Servers
richdoes.com uses two name servers for its delegation: ns21.domaincontrol.com and ns22.domaincontrol.com.
The name server configuration of richdoes.com is shared with other domains, for instance janhan.com, duplicators.net, seldakoydemir.com and two others.
At least some of richdoes.com's name servers are also used by other domains, among them hensel-electric.com.tr.
The two host names ns21.domaincontrol.com and ns22.domaincontrol.com each have a pair of IP addresses: ns21.domaincontrol.com has 97.74.100.11 and 2603:5:2141::b, and ns22.domaincontrol.com has 173.201.68.11 and 2603:5:2241::b.
Mail Servers
Mail for richdoes.com is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
At least some of the mail servers used by richdoes.com are shared with other domains: arxa.ca, alpernmedia.com, americanfortress.io 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 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 142.250.31.26 and 2607:f8b0:4004:c06::1a.
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.26 and 2a00:1450:400b:c02::1a.