pyter.dev - robtex.com
pyter.dev
| DNSSEC | ⚠️ Not signed | ||||||
| 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@pyter.dev serial=0 | ||||||
dev
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
Similar names
Previous names
pysh.dev |
pyshah.dev |
pysight.dev |
pysm.dev |
pysof.dev |
pysolutions.dev |
pyspot.dev |
pyspur.dev |
pyst.dev |
pystack.dev |
pystar.dev |
pystim.dev |
pyswap.dev |
pyszkowski.dev |
pyt.dev |
pytan.dev |
pyte.dev |
pytec.dev |
pytech.dev |
pytel.dev |
Next names
DNS History
3 records (3 active, 0 former)
●NSns1.digitalocean.com2026-09-19 → 2026-09-27 · 2 obs
● 2026-09-27 11:13:34
●NSns2.digitalocean.com2026-09-19 → 2026-09-27 · 2 obs
● 2026-09-27 11:13:34
●NSns3.digitalocean.com2026-09-19 → 2026-09-27 · 2 obs
● 2026-09-27 11:13:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld3.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com... | - |
| pyter.dev | ns1.digitalocean.com, ns3.digitalocean.com, ns2.digitalocean.com | - |
✅ Authoritative Response
Server:172.64.53.21
NS records: ns1.digitalocean.com, ns3.digitalocean.com, ns2.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for pyter.dev (unsigned zone)
⏱️ Timing
Total: 732ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 3 | ns2.digitalocean.com, ns1.digitalocean.com... |
| SOA | 1 | ns1.digitalocean.com hostmaster.pyter.de |
Analysis
Name Servers
The authoritative name servers for pyter.dev are ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com — three in total.
There is at least partial name server overlap between pyter.dev and other domains — stylistthreading.com, marios.com.gr, tvunna.com and two more among them.
ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com all resolve to exactly two IP numbers apiece: ns1.digitalocean.com → 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com → 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com → 172.64.49.209 and 2606:4700:52::ac40:31d1.