well-known.dev - robtex.com
well-known.dev
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 | ||||||
🔒 HSTS Preload (+subdomains)
Same first word
well-known.dev |
well-known.online |
well-known.org |
DNS History
6 records (6 active, 0 former)
●NSns1.digitalocean.com2026-02-27 → 2026-04-03 · 2 obs
● 2026-04-03 08:43:24
●NSns2.digitalocean.com2026-02-27 → 2026-04-03 · 2 obs
● 2026-04-03 08:43:24
●NSns3.digitalocean.com2026-02-27 → 2026-04-03 · 2 obs
● 2026-04-03 08:43:24
●MXin1-smtp.messagingengine.com2026-02-27 → 2026-04-03 · 2 obs
● 2026-04-03 08:43:24
●MXin2-smtp.messagingengine.com2026-02-27 → 2026-04-03 · 2 obs
● 2026-04-03 08:43:24
●A146.190.194.1872026-02-27 → 2026-04-03 · 2 obs
● 2026-04-03 08:43:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | 10 records |
| well-known.dev | ns3.digitalocean.com, ns2.digitalocean.com, ns1.digitalocean.com | - |
✅ Authoritative Response
Server:172.64.52.210
NS records: ns3.digitalocean.com, ns2.digitalocean.com, ns1.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for well-known.dev (unsigned zone)
⏱️ Timing
Total: 438ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 146.190.194.187 |
| NS | 3 | ns2.digitalocean.com, ns3.digitalocean.com... |
| MX | 2 | in2-smtp.messagingengine.com (pri: 20), in1-smtp.messagingengine.com (pri: 10) |
| TXT | 3 | abuseipdb-verification=BnFjEBBx, v=spf1 include:spf.messagingengine.com ?... |
| SOA | 1 | ns1.digitalocean.com hostmaster.well-kno |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
IP Addresses
well-known.dev resolves to one IP number: 146.190.194.187.
Other host names, for instance jmvickers.com, resisty.com and projectalias.com share IP numbers with well-known.dev.
Name Servers
well-known.dev is delegated to three name servers ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.
well-known.dev at least partially shares name servers with other domains, for instance 138.183.68.in-addr.arpa, 70.166.188.in-addr.arpa, foodmyfood.com, 3.85.95.in-addr.arpa and 162.209.134.in-addr.arpa.
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.
Mail Servers
Two mail servers handle well-known.dev: in1-smtp.messagingengine.com and in2-smtp.messagingengine.com.
well-known.dev shares the same mail server setup as other domains, for instance froosh.net, michaelbeer.net, yaki.org, gregloesch.com and johneo.com.
Host names with eight IPs:
in1-smtp.messagingengine.com points to 103.168.172.216103.168.172.217103.168.172.218103.168.172.219103.168.172.220103.168.172.221103.168.172.222 and 103.168.172.223.
Host names with four IPs:
in2-smtp.messagingengine.com points to 202.12.124.216202.12.124.217202.12.124.218 and 202.12.124.219.