dr23.com - dns.ninja
dr23.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=1784490772 | ||||||
Same first word
Similar names
DNS History
18 records (6 active, 12 former)
●NSns1.name.com2026-07-08 → 2026-07-19 · 3 obs
● 2026-07-08 07:38:58
● 2026-07-19 20:22:20
○NSns1.sedoparking.com2015-10-20 → 2026-04-12 · 5 obs
● 2015-10-20 17:56:22
● 2026-04-12 10:51:30
○ 2026-07-08 07:38:58
○ 2026-07-19 20:22:20
●NSns1cny.name.com2026-07-08 → 2026-07-19 · 3 obs
● 2026-07-08 07:38:58
● 2026-07-19 20:22:20
○NSns2.sedoparking.com2015-10-20 → 2026-04-12 · 5 obs
● 2015-10-20 17:56:22
● 2026-04-12 10:51:30
○ 2026-07-08 07:38:58
○ 2026-07-19 20:22:20
●NSns2kry.name.com2026-07-08 → 2026-07-19 · 3 obs
● 2026-07-08 07:38:58
● 2026-07-19 20:22:20
●NSns3dkz.name.com2026-07-08 → 2026-07-19 · 3 obs
● 2026-07-08 07:38:58
● 2026-07-19 20:22:20
○NSns49.domaincontrol.com2015-05-17 → 2015-05-17 · 3 obs
○ 2015-10-20 17:56:22
○ 2026-07-19 20:22:20
●NSns4bht.name.com2026-07-08 → 2026-07-19 · 3 obs
● 2026-07-08 07:38:58
● 2026-07-19 20:22:20
○NSns50.domaincontrol.com2015-05-17 → 2015-05-17 · 3 obs
○ 2015-10-20 17:56:22
○ 2026-07-19 20:22:20
○MXlocalhost2017-02-03 → 2026-04-12 · 5 obs
● 2017-02-03 21:18:54
● 2026-04-12 10:51:30
○ 2026-07-08 07:38:58
○ 2026-07-19 20:22:20
○MXmail.nickstel.com2015-10-20 → 2016-03-29 · 5 obs
● 2015-10-20 17:56:22
● 2016-03-29 11:51:22
○ 2017-02-03 21:18:54
○ 2026-07-19 20:22:20
○MXmailstore1.secureserver.net2015-05-17 → 2015-05-17 · 3 obs
○ 2015-10-20 17:56:22
○ 2026-07-19 20:22:20
○MXsmtp.secureserver.net2015-05-17 → 2015-05-17 · 3 obs
○ 2015-10-20 17:56:22
○ 2026-07-19 20:22:20
○A184.168.221.392015-05-17 → 2015-05-17 · 3 obs
○ 2015-10-20 17:56:22
○ 2026-07-19 20:22:20
○A64.190.63.2222026-03-05 → 2026-04-12 · 5 obs
● 2026-03-05 10:32:24
● 2026-04-12 10:51:30
○ 2026-07-08 07:38:58
○ 2026-07-19 20:22:20
○A72.52.4.1192015-10-20 → 2017-02-03 · 5 obs
● 2015-10-20 17:56:22
● 2017-02-03 21:18:54
○ 2019-03-23 02:01:50
○ 2026-07-19 20:22:20
●A75.126.100.72026-07-08 → 2026-07-19 · 3 obs
● 2026-07-08 07:38:58
● 2026-07-19 20:22:20
○A91.195.240.1262019-03-23 → 2019-03-23 · 4 obs
● 2019-03-23 02:01:50
○ 2026-03-05 10:32:24
○ 2026-07-19 20:22:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, a.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net... | - |
| dr23.com | ns1cny.name.com, ns2kry.name.com, ns3dkz.name.com, ns4bht.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.17
NS records: ns1cny.name.com, ns2kry.name.com, ns3dkz.name.com, ns4bht.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for dr23.com (unsigned zone)
⏱️ Timing
Total: 393ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 75.126.100.7 |
| NS | 4 | ns1cny.name.com, ns2kry.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1cny.name.com, ns1cny.name.com, ns2kry.name.com...)
Analysis
IP Addresses
dr23.com resolves to just one IP address, 75.126.100.7.
Two other host names, along with daddyfest.com, (0x706f726e687562)network.com and ilkten.com, also share IP numbers with dr23.com.
Name Servers
dr23.com delegates to five name servers: ns1.name.com, ns1cny.name.com, ns2kry.name.com and two others.
The name servers of dr23.com overlap at least partially with those of other domains — among them marydrew.com, 91p02.space, bighornclub.org and two more.
These name servers commonly appear in delegations together with ns4bht.name.com, ns3dkz.name.com, ns3jkl.name.com and 7 other.
Host names that have two IP addresses:
ns1.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns1cny.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns2kry.name.com resolves to two addresses: 163.114.216.49 and 2402:cf80:107::1.
ns3dkz.name.com resolves to two addresses: 163.114.217.17 and 2a00:edc0:107::49.
ns4bht.name.com resolves to two addresses: 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com along with ns1cny.name.com each resolve to 2a00:edc0:107::1 IP addresses.
ns1.name.com along with ns1cny.name.com each resolve to 163.114.216.17 IP addresses.