puroman.com - robtex.com
puroman.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.digitalocean.com ⚠️ Not in zone NS records | ||||||
| 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 ⚠️ Not in zone NS records | ||||||
| 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 ⚠️ Not in zone NS records | ||||||
| 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 | ||||||
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
puroman.com |
Similar names
DNS History
13 records (3 active, 10 former)
○NSjm1.dns.com2020-03-22 → 2020-03-22 · 4 obs
○ 2017-04-06 18:06:32
● 2020-03-22 08:22:36
○ 2026-03-09 08:56:24
○ 2026-03-23 23:28:06
● 2020-03-22 08:22:36
○ 2026-03-09 08:56:24
○ 2026-03-23 23:28:06
○NSjm2.dns.com2020-03-22 → 2020-03-22 · 4 obs
○ 2017-04-06 18:06:32
● 2020-03-22 08:22:36
○ 2026-03-09 08:56:24
○ 2026-03-23 23:28:06
● 2020-03-22 08:22:36
○ 2026-03-09 08:56:24
○ 2026-03-23 23:28:06
○NSns-fr.1and1-dns.biz2015-05-21 → 2017-04-06 · 4 obs
● 2015-05-21 02:28:02
● 2017-04-06 18:06:32
○ 2020-03-22 08:22:36
○ 2026-03-23 23:28:06
● 2017-04-06 18:06:32
○ 2020-03-22 08:22:36
○ 2026-03-23 23:28:06
○NSns-fr.1and1-dns.com2015-05-21 → 2017-04-06 · 4 obs
● 2015-05-21 02:28:02
● 2017-04-06 18:06:32
○ 2020-03-22 08:22:36
○ 2026-03-23 23:28:06
● 2017-04-06 18:06:32
○ 2020-03-22 08:22:36
○ 2026-03-23 23:28:06
○NSns-fr.1and1-dns.fr2015-05-21 → 2017-04-06 · 4 obs
● 2015-05-21 02:28:02
● 2017-04-06 18:06:32
○ 2020-03-22 08:22:36
○ 2026-03-23 23:28:06
● 2017-04-06 18:06:32
○ 2020-03-22 08:22:36
○ 2026-03-23 23:28:06
○NSns-fr.1and1-dns.org2015-05-21 → 2017-04-06 · 4 obs
● 2015-05-21 02:28:02
● 2017-04-06 18:06:32
○ 2020-03-22 08:22:36
○ 2026-03-23 23:28:06
● 2017-04-06 18:06:32
○ 2020-03-22 08:22:36
○ 2026-03-23 23:28:06
●NSns1.digitalocean.com2026-03-09 → 2026-03-23 · 3 obs
○ 2020-03-22 08:22:36
● 2026-03-09 08:56:24
● 2026-03-23 23:28:06
● 2026-03-09 08:56:24
● 2026-03-23 23:28:06
●NSns2.digitalocean.com2026-03-09 → 2026-03-23 · 3 obs
○ 2020-03-22 08:22:36
● 2026-03-09 08:56:24
● 2026-03-23 23:28:06
● 2026-03-09 08:56:24
● 2026-03-23 23:28:06
●NSns3.digitalocean.com2026-03-09 → 2026-03-23 · 3 obs
○ 2020-03-22 08:22:36
● 2026-03-09 08:56:24
● 2026-03-23 23:28:06
● 2026-03-09 08:56:24
● 2026-03-23 23:28:06
○MXmx00.1and1.fr2015-05-21 → 2017-04-06 · 4 obs
● 2015-05-21 02:28:02
● 2017-04-06 18:06:32
○ 2026-03-09 08:56:24
○ 2026-03-23 23:28:06
● 2017-04-06 18:06:32
○ 2026-03-09 08:56:24
○ 2026-03-23 23:28:06
○MXmx01.1and1.fr2015-05-21 → 2017-04-06 · 4 obs
● 2015-05-21 02:28:02
● 2017-04-06 18:06:32
○ 2026-03-09 08:56:24
○ 2026-03-23 23:28:06
● 2017-04-06 18:06:32
○ 2026-03-09 08:56:24
○ 2026-03-23 23:28:06
○A45.199.219.502020-03-22 → 2020-03-22 · 4 obs
○ 2017-04-06 18:06:32
● 2020-03-22 08:22:36
○ 2026-03-09 08:56:24
○ 2026-03-23 23:28:06
● 2020-03-22 08:22:36
○ 2026-03-09 08:56:24
○ 2026-03-23 23:28:06
○A92.222.37.1672015-05-21 → 2017-04-06 · 4 obs
● 2015-05-21 02:28:02
● 2017-04-06 18:06:32
○ 2020-03-22 08:22:36
○ 2026-03-23 23:28:06
● 2017-04-06 18:06:32
○ 2020-03-22 08:22:36
○ 2026-03-23 23:28:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net, e.gtld-servers.net... | - |
| puroman.com | ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com | 3 records |
✅ Authoritative Response
Server:172.64.49.209
NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for puroman.com (unsigned zone)
⏱️ Timing
Total: 126ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 3
Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)
Analysis
Name Servers
puroman.com is delegated to three name servers ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.
puroman.com at least partially shares name servers with other domains, for instance devcodes.co, mluts.net, 85.65.159.in-addr.arpa, hostexpert.us and soarpointmassage.com.
Host names with two IP numbers:
ns1.digitalocean.com points to: 2606:4700:52::ac40:34d2 and 172.64.52.210.
ns2.digitalocean.com points to: 2606:4700:5a::ac40:3515 and 172.64.53.21.
ns3.digitalocean.com points to: 2606:4700:52::ac40:31d1 and 172.64.49.209.