why-fire.com - dns.ninja
why-fire.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 | ns23.domaincontrol.com ⭐ | ||||||
| A | 2603:5:2151::c🇺🇸 GODADDY-DNS2603:5:2150::/44 | ||||||
| PTR | ns23.domaincontrol.com | ||||||
| A | 97.74.101.12🇺🇸 GODADDY-DNS97.74.100.0/23 | ||||||
| PTR | ns23.domaincontrol.com | ||||||
| NS | ns24.domaincontrol.com | ||||||
| A | 2603:5:2251::c🇺🇸 GODADDY-DNS2603:5:2250::/44 | ||||||
| PTR | ns24.domaincontrol.com | ||||||
| A | 173.201.69.12🇺🇸 GODADDY-DNS173.201.68.0/23 | ||||||
| PTR | ns24.domaincontrol.com | ||||||
| SOA | ns23.domaincontrol.comdns@jomax.net 2023-09-19 #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=1782641655 | ||||||
Previously MX for
why-fire.com |
Same first word
why-fire.com |
DNS History
8 records (4 active, 4 former)
○NSns1.why-fire.com2017-05-08 → 2017-05-08 · 3 obs
○ 2026-04-24 23:04:12
○ 2026-06-28 10:29:46
○NSns2.why-fire.com2017-05-08 → 2017-05-08 · 3 obs
○ 2026-04-24 23:04:12
○ 2026-06-28 10:29:46
●NSns23.domaincontrol.com2026-04-24 → 2026-06-28 · 3 obs
● 2026-04-24 23:04:12
● 2026-06-28 10:29:46
●NSns24.domaincontrol.com2026-04-24 → 2026-06-28 · 3 obs
● 2026-04-24 23:04:12
● 2026-06-28 10:29:46
○MXwhy-fire.com2017-05-08 → 2017-05-08 · 3 obs
○ 2026-04-24 23:04:12
○ 2026-06-28 10:29:46
●A15.197.148.332026-04-24 → 2026-06-28 · 3 obs
● 2026-04-24 23:04:12
● 2026-06-28 10:29:46
○A198.57.210.1032017-05-08 → 2017-05-08 · 3 obs
○ 2026-04-24 23:04:12
○ 2026-06-28 10:29:46
●A3.33.130.1902026-04-24 → 2026-06-28 · 3 obs
● 2026-04-24 23:04:12
● 2026-06-28 10:29:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| why-fire.com | ns23.domaincontrol.com, ns24.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.69.12
NS records: ns23.domaincontrol.com, ns24.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for why-fire.com (unsigned zone)
⏱️ Timing
Total: 89ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 3.33.130.190, 15.197.148.33 |
| NS | 2 | ns23.domaincontrol.com, ns24.domaincontrol.com |
| SOA | 1 | ns23.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns23.domaincontrol.com, ns23.domaincontrol.com, ns24.domaincontrol.com...)
Analysis
IP Addresses
why-fire.com directs to two IP numbers, 3.33.130.190 and 15.197.148.33
Among the host names that share IP numbers with why-fire.com are carepaxs.com, guyi.me, executivebusiness.org and two others.
Name Servers
Two name servers handle the delegation for why-fire.com: ns23.domaincontrol.com and ns24.domaincontrol.com.
why-fire.com has the same name server delegation as a number of other domains, such as cyger.media, globaltechpay.com, emma-marie.com and two more.
ns23.domaincontrol.com and ns24.domaincontrol.com both carry two IP addresses. The A records for ns23.domaincontrol.com are 97.74.101.12 and 2603:5:2151::c; the A records for ns24.domaincontrol.com are 173.201.69.12 and 2603:5:2251::c.