bd384.com - dns.ninja
bd384.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 23.224.228.83 | ||||||
| NS | ns1.mcpfks.com ⚠️ Not in zone NS records | ||||||
| NS | ns2.mcpfks.com ⚠️ Not in zone NS records | ||||||
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=1782948621 | ||||||
Same first word
bd384.com |
Similar names
DNS History
12 records (3 active, 9 former)
●NSns1.mcpfks.com2026-04-23 → 2026-07-01 · 3 obs
○ 2026-04-05 11:00:56
● 2026-04-23 11:39:16
● 2026-07-01 23:55:32
● 2026-04-23 11:39:16
● 2026-07-01 23:55:32
○NSns17.domaincontrol.com2026-04-03 → 2026-04-05 · 5 obs
○ 2019-12-18 06:49:28
● 2026-04-03 21:05:22
● 2026-04-05 11:00:56
○ 2026-04-23 11:39:16
○ 2026-07-01 23:55:32
● 2026-04-03 21:05:22
● 2026-04-05 11:00:56
○ 2026-04-23 11:39:16
○ 2026-07-01 23:55:32
○NSns18.domaincontrol.com2026-04-03 → 2026-04-05 · 5 obs
○ 2019-12-18 06:49:28
● 2026-04-03 21:05:22
● 2026-04-05 11:00:56
○ 2026-04-23 11:39:16
○ 2026-07-01 23:55:32
● 2026-04-03 21:05:22
● 2026-04-05 11:00:56
○ 2026-04-23 11:39:16
○ 2026-07-01 23:55:32
●NSns2.mcpfks.com2026-04-23 → 2026-07-01 · 3 obs
○ 2026-04-05 11:00:56
● 2026-04-23 11:39:16
● 2026-07-01 23:55:32
● 2026-04-23 11:39:16
● 2026-07-01 23:55:32
○NSns7.alidns.com2019-12-18 → 2019-12-18 · 3 obs
● 2019-12-18 06:49:28
○ 2026-04-03 21:05:22
○ 2026-07-01 23:55:32
○ 2026-04-03 21:05:22
○ 2026-07-01 23:55:32
○NSns8.alidns.com2019-12-18 → 2019-12-18 · 3 obs
● 2019-12-18 06:49:28
○ 2026-04-03 21:05:22
○ 2026-07-01 23:55:32
○ 2026-04-03 21:05:22
○ 2026-07-01 23:55:32
○A13.248.213.452026-04-03 → 2026-04-05 · 5 obs
○ 2019-12-18 06:49:28
● 2026-04-03 21:05:22
● 2026-04-05 11:00:56
○ 2026-04-23 11:39:16
○ 2026-07-01 23:55:32
● 2026-04-03 21:05:22
● 2026-04-05 11:00:56
○ 2026-04-23 11:39:16
○ 2026-07-01 23:55:32
○A15.197.148.332026-04-03 → 2026-07-01 · 2 obs
○ 2026-04-03 21:05:22
○ 2026-07-01 23:55:32
○ 2026-07-01 23:55:32
○A198.15.236.2342019-12-18 → 2019-12-18 · 3 obs
● 2019-12-18 06:49:28
○ 2026-04-03 21:05:22
○ 2026-07-01 23:55:32
○ 2026-04-03 21:05:22
○ 2026-07-01 23:55:32
●A23.224.228.832026-04-23 → 2026-07-01 · 3 obs
○ 2026-04-05 11:00:56
● 2026-04-23 11:39:16
● 2026-07-01 23:55:32
● 2026-04-23 11:39:16
● 2026-07-01 23:55:32
○A3.33.130.1902026-04-03 → 2026-07-01 · 2 obs
○ 2026-04-03 21:05:22
○ 2026-07-01 23:55:32
○ 2026-07-01 23:55:32
○A76.223.67.1892026-04-03 → 2026-04-05 · 5 obs
○ 2019-12-18 06:49:28
● 2026-04-03 21:05:22
● 2026-04-05 11:00:56
○ 2026-04-23 11:39:16
○ 2026-07-01 23:55:32
● 2026-04-03 21:05:22
● 2026-04-05 11:00:56
○ 2026-04-23 11:39:16
○ 2026-07-01 23:55:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, d.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net... | - |
| bd384.com | ns1.mcpfks.com, ns2.mcpfks.com | 2 records |
✅ Authoritative Response
Server:8.134.173.183
NS records: ns1.mcpfks.com, ns2.mcpfks.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bd384.com (unsigned zone)
⏱️ Timing
Total: 868ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.224.132.187 |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.mcpfks.com, ns2.mcpfks.com)
Analysis
IP Addresses
bd384.com has exactly one IP address — 23.224.228.83.
Name Servers
bd384.com is served by two delegated name servers, ns1.mcpfks.com and ns2.mcpfks.com.