rmcoding.com - robtex.com
rmcoding.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 138.197.70.237🇺🇸 DIGITALOCEAN138.197.64.0/20 DigitalOcean | ||||||
| NS | ns1.digitalocean.com ⭐ | ||||||
| A | 2606:4700:52::ac40:34d2🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| A | 172.64.52.210🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| NS | ns2.digitalocean.com | ||||||
| A | 2606:4700:5a::ac40:3515🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| A | 172.64.53.21🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| NS | ns3.digitalocean.com | ||||||
| A | 2606:4700:52::ac40:31d1🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| A | 172.64.49.209🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| SOA | ns1.digitalocean.comhostmaster@rmcoding.com serial=0 | ||||||
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=1790127539 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
16 records (4 active, 12 former)
●NSns1.digitalocean.com2016-12-15 → 2026-09-23 · 2 obs
● 2026-09-23 01:44:58
○NSns1.linode.com2017-10-18 → 2017-10-18 · 4 obs
● 2017-10-18 21:47:52
○ 2026-09-03 12:43:54
○ 2026-09-23 01:44:58
●NSns2.digitalocean.com2016-12-15 → 2026-09-23 · 4 obs
○ 2017-10-18 21:47:52
● 2026-09-03 12:43:54
● 2026-09-23 01:44:58
○NSns2.linode.com2017-10-18 → 2017-10-18 · 4 obs
● 2017-10-18 21:47:52
○ 2026-09-03 12:43:54
○ 2026-09-23 01:44:58
●NSns3.digitalocean.com2016-12-15 → 2026-09-23 · 4 obs
○ 2017-10-18 21:47:52
● 2026-09-03 12:43:54
● 2026-09-23 01:44:58
○NSns3.linode.com2017-10-18 → 2017-10-18 · 4 obs
● 2017-10-18 21:47:52
○ 2026-09-03 12:43:54
○ 2026-09-23 01:44:58
○NSns4.linode.com2017-10-18 → 2017-10-18 · 4 obs
● 2017-10-18 21:47:52
○ 2026-09-03 12:43:54
○ 2026-09-23 01:44:58
○NSns5.linode.com2017-10-18 → 2017-10-18 · 4 obs
● 2017-10-18 21:47:52
○ 2026-09-03 12:43:54
○ 2026-09-23 01:44:58
○MXalt1.aspmx.l.google.com2016-12-15 → 2016-12-15 · 3 obs
○ 2017-10-18 21:47:52
○ 2026-09-23 01:44:58
○MXalt2.aspmx.l.google.com2016-12-15 → 2016-12-15 · 3 obs
○ 2017-10-18 21:47:52
○ 2026-09-23 01:44:58
○MXalt3.aspmx.l.google.com2016-12-15 → 2016-12-15 · 3 obs
○ 2017-10-18 21:47:52
○ 2026-09-23 01:44:58
○MXalt4.aspmx.l.google.com2016-12-15 → 2016-12-15 · 3 obs
○ 2017-10-18 21:47:52
○ 2026-09-23 01:44:58
○MXaspmx.l.google.com2016-12-15 → 2016-12-15 · 3 obs
○ 2017-10-18 21:47:52
○ 2026-09-23 01:44:58
●A138.197.70.2372026-09-03 → 2026-09-23 · 3 obs
● 2026-09-03 12:43:54
● 2026-09-23 01:44:58
○A45.33.7.2452017-10-18 → 2017-10-18 · 4 obs
● 2017-10-18 21:47:52
○ 2026-09-03 12:43:54
○ 2026-09-23 01:44:58
○A45.55.65.2262016-12-15 → 2016-12-15 · 3 obs
○ 2017-10-18 21:47:52
○ 2026-09-23 01:44:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, a.gtld-servers.net, c.gtld-servers.net, i.gtld-servers.net... | - |
| rmcoding.com | ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com | 3 records |
✅ Authoritative Response
Server:172.64.52.210
NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for rmcoding.com (unsigned zone)
⏱️ Timing
Total: 766ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 138.197.70.237 |
| NS | 3 | ns3.digitalocean.com, ns1.digitalocean.com... |
| SOA | 1 | ns1.digitalocean.com hostmaster.rmcoding |
📌 Glue Records Collected
Total: 3
Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)
Analysis
IP Addresses
rmcoding.com resolves to one IP address: 138.197.70.237.
Name Servers
rmcoding.com is delegated to three name servers: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.
At least some of rmcoding.com's name servers are shared with other domains, for example chrisrogusvoice.com, sapogin.com, swadeshika.com and two more.
These name servers tend to be used in conjunction with the name servers ns4.digitalocean.com.
ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com each resolve to two IP addresses: ns1.digitalocean.com resolves to 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com resolves to 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com resolves to 172.64.49.209 and 2606:4700:52::ac40:31d1.