dftin.com - dns.ninja
dftin.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 3.33.130.190🇺🇸 Amazon3.33.128.0/20 | ||||||
| PTR | a2aa9ff50de748dbe.awsglobalaccelerator.com | ||||||
| A | 15.197.148.33🇺🇸 Amazon15.197.144.0/20 | ||||||
| NS | ns37.domaincontrol.com ⭐ | ||||||
| A | 2603:5:21c1::13🇺🇸 GODADDY-DNS2603:5:21c0::/44 | ||||||
| PTR | ns37.domaincontrol.com | ||||||
| A | 97.74.108.19🇺🇸 GODADDY-DNS97.74.108.0/23 | ||||||
| PTR | ns37.domaincontrol.com | ||||||
| NS | ns38.domaincontrol.com | ||||||
| A | 2603:5:22c1::13🇺🇸 GODADDY-DNS2603:5:22c0::/44 | ||||||
| PTR | ns38.domaincontrol.com | ||||||
| A | 173.201.76.19🇺🇸 GODADDY-DNS173.201.76.0/23 | ||||||
| PTR | ns38.domaincontrol.com | ||||||
| SOA | ns37.domaincontrol.comdns@jomax.net 2023-09-20 #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=1785015052 | ||||||
Same first word
dftin.com |
Similar names
DNS History
11 records (4 active, 7 former)
●NSns37.domaincontrol.com2026-03-27 → 2026-07-25 · 3 obs
● 2026-03-27 20:45:36
● 2026-07-25 21:45:34
●NSns38.domaincontrol.com2026-03-27 → 2026-07-25 · 3 obs
● 2026-03-27 20:45:36
● 2026-07-25 21:45:34
○NSns73.domaincontrol.com2015-08-13 → 2017-03-26 · 4 obs
● 2017-03-26 02:41:28
○ 2026-03-27 20:45:36
○ 2026-07-25 21:45:34
○NSns74.domaincontrol.com2015-08-13 → 2017-03-26 · 4 obs
● 2017-03-26 02:41:28
○ 2026-03-27 20:45:36
○ 2026-07-25 21:45:34
○MXmail.dftin.com2016-06-26 → 2017-03-26 · 5 obs
● 2016-06-26 18:02:04
● 2017-03-26 02:41:28
○ 2026-03-27 20:45:36
○ 2026-07-25 21:45:34
○MXmailstore1.secureserver.net2015-08-13 → 2016-03-11 · 4 obs
● 2016-03-11 06:27:40
○ 2016-06-26 18:02:04
○ 2026-07-25 21:45:34
○MXsmtp.secureserver.net2015-08-13 → 2016-03-11 · 4 obs
● 2016-03-11 06:27:40
○ 2016-06-26 18:02:04
○ 2026-07-25 21:45:34
●A15.197.148.332026-03-27 → 2026-07-25 · 3 obs
● 2026-03-27 20:45:36
● 2026-07-25 21:45:34
○A184.168.221.342016-06-26 → 2017-03-26 · 5 obs
● 2016-06-26 18:02:04
● 2017-03-26 02:41:28
○ 2026-03-27 20:45:36
○ 2026-07-25 21:45:34
○A184.168.221.532015-08-13 → 2016-03-11 · 4 obs
● 2016-03-11 06:27:40
○ 2016-06-26 18:02:04
○ 2026-07-25 21:45:34
●A3.33.130.1902026-03-27 → 2026-07-25 · 3 obs
● 2026-03-27 20:45:36
● 2026-07-25 21:45:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| dftin.com | ns37.domaincontrol.com, ns38.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.108.19
NS records: ns37.domaincontrol.com, ns38.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for dftin.com (unsigned zone)
⏱️ Timing
Total: 148ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 3.33.130.190, 15.197.148.33 |
| NS | 2 | ns37.domaincontrol.com, ns38.domaincontrol.com |
| SOA | 1 | ns37.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns37.domaincontrol.com, ns37.domaincontrol.com, ns38.domaincontrol.com...)
Analysis
IP Addresses
dftin.com directs to two IP numbers, 3.33.130.190 and 15.197.148.33
heypickle.com, bruningandassociates.com, machaan.co.in plus two other host names have IP numbers in common with dftin.com.
Name Servers
The NS records for dftin.com delegate to ns37.domaincontrol.com and ns38.domaincontrol.com.
The name server configuration of dftin.com is shared with other domains, for instance towerbaptistonaway.com, marathon.events, frankeltime.com and two others.
ns37.domaincontrol.com resolves to 97.74.108.19 and 2603:5:21c1::13. Likewise, ns38.domaincontrol.com resolves to 173.201.76.19 and 2603:5:22c1::13 — two IP addresses apiece.