rmnaples.com - robtex.com
rmnaples.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=1771291435 | ||||||
Same first word
rmnaples.com |
Similar names
DNS History
8 records (8 active, 0 former)
●NSns71.domaincontrol.com2026-02-27 → 2026-03-11 · 2 obs
● 2026-03-11 13:30:36
●NSns72.domaincontrol.com2026-02-27 → 2026-03-11 · 2 obs
● 2026-03-11 13:30:36
●MXalt1.aspmx.l.google.com2026-02-27 → 2026-03-11 · 2 obs
● 2026-03-11 13:30:36
●MXalt2.aspmx.l.google.com2026-02-27 → 2026-03-11 · 2 obs
● 2026-03-11 13:30:36
●MXalt3.aspmx.l.google.com2026-02-27 → 2026-03-11 · 2 obs
● 2026-03-11 13:30:36
●MXalt4.aspmx.l.google.com2026-02-27 → 2026-03-11 · 2 obs
● 2026-03-11 13:30:36
●MXaspmx.l.google.com2026-02-27 → 2026-03-11 · 2 obs
● 2026-03-11 13:30:36
●A216.37.42.2062026-02-27 → 2026-03-11 · 2 obs
● 2026-03-11 13:30:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, m.gtld-servers.net, i.gtld-servers.net, b.gtld-servers.net... | - |
| rmnaples.com | ns71.domaincontrol.com, ns72.domaincontrol.com | 4 records |
✅ Authoritative Response
Server: 97.74.105.46
NS records: ns71.domaincontrol.com, ns72.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for rmnaples.com (unsigned zone)
⏱️ Timing
Total: 405ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 216.37.42.206 |
| NS | 2 | ns71.domaincontrol.com, ns72.domaincontrol.com |
| MX | 5 | alt4.aspmx.l.google.com (pri: 10), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | v=spf1 include:dc-aa8e722993._spfm.rmnap, google-site-verification=qE3RVZYJ9tt4Jha |
| SOA | 1 | ns71.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns71.domaincontrol.com, ns71.domaincontrol.com, ns72.domaincontrol.com...)
Analysis
IP Addresses
rmnaples.com maps to IP address 216.37.42.206.
Other host names, for instance hhjinc.com, bgcnewbedford.org, riodelsolkiwanis.com, mauzelawfirm.com and fundraisingcoach.com share IP numbers with rmnaples.com.
Name Servers
Two name servers ns71.domaincontrol.com and ns72.domaincontrol.com are delegated to rmnaples.com.
rmnaples.com uses the same name server configuration as other domains, such as hvmc.net, gencell.net, meet-and-work.com, aportamx.com and capecodcraftbeer.beer.
rmnaples.com shares some name servers with other domains, for example icbc.co.in.
Host names with two IPs:
ns71.domaincontrol.com points to 2603:5:2194::2e and 97.74.105.46.
ns72.domaincontrol.com points to 2603:5:2294::2e and 173.201.73.46.
Mail Servers
rmnaples.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.
rmnaples.com shares mail servers with other domains at least in part, for instance g-apps.fisherautoparts.com, topspot.ph, qventures.org, couplesunity.wpengine.com and ns500759.ns500759.ns500759.ns500698.ns500759.ns500736.ns500735.ns500735.ns500735.ns500698.ns500576.ns500576.ns500576.ns500652.trackreceptor.com.
These mail servers are often used together with aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Two IPs per host name:
aspmx.l.google.com points to: 2607:f8b0:4004:c19::1b and 172.253.62.27
alt1.aspmx.l.google.com points to: 2607:f8b0:4003:c30::1b and 74.125.27.26
alt2.aspmx.l.google.com points to: 2607:f8b0:4001:c70::1a and 192.178.209.26
alt3.aspmx.l.google.com points to: 2607:f8b0:4024:c0d::1b and 192.178.152.26
alt4.aspmx.l.google.com points to: 2607:f8b0:4023:403::1a and 142.250.96.27
Pattern: left IDs ascend by 9 (12, 21, 30, 39, 48); each pair of targets ascend by 9 (15/18, 24/27, 33/36, 42/45, 51/54)