fdbk.com - dns.ninja
fdbk.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=1781532975 | ||||||
Same first word
fdbk.com |
fdbk.su |
fdbk.de |
fdbk.biz |
fdbk.net |
fdbk.ru |
fdbk.cn |
fdbk.hateblo.jp |
fdbk.com.ar |
fdbk.co |
fdbk.nl |
fdbk.at |
fdbk.pl |
fdbk.us |
Similar names
DNS History
9 records (9 active, 0 former)
●NSdns1.stabletransit.com2015-08-01 → 2026-06-15 · 2 obs
● 2026-06-15 14:33:54
●NSdns2.stabletransit.com2015-08-01 → 2026-06-15 · 2 obs
● 2026-06-15 14:33:54
●NSns.rackspace.com2015-08-01 → 2026-06-15 · 2 obs
● 2026-06-15 14:33:54
●MXalt1.aspmx.l.google.com2015-08-01 → 2026-06-15 · 2 obs
● 2026-06-15 14:33:54
●MXalt2.aspmx.l.google.com2015-08-01 → 2026-06-15 · 2 obs
● 2026-06-15 14:33:54
●MXalt3.aspmx.l.google.com2015-08-01 → 2026-06-15 · 2 obs
● 2026-06-15 14:33:54
●MXalt4.aspmx.l.google.com2015-08-01 → 2026-06-15 · 2 obs
● 2026-06-15 14:33:54
●MXaspmx.l.google.com2015-08-01 → 2026-06-15 · 2 obs
● 2026-06-15 14:33:54
●A162.209.106.1642015-08-01 → 2026-06-15 · 2 obs
● 2026-06-15 14:33:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| fdbk.com | dns1.stabletransit.com, dns2.stabletransit.com | 2 records |
✅ Authoritative Response
Server:65.61.188.4
NS records: dns1.stabletransit.com, dns2.stabletransit.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fdbk.com (unsigned zone)
⏱️ Timing
Total: 294ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 162.209.106.164 |
| NS | 2 | dns1.stabletransit.com, dns2.stabletransit.com |
| MX | 5 | ALT2.ASPMX.L.GOOGLE.COM (pri: 5), ALT3.ASPMX.L.GOOGLE.COM (pri: 10)... |
| TXT | 1 | google-site-verification=NYDxRhdj4p2oeCw |
| SOA | 1 | ns.rackspace.com noreply.fdbk.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (dns1.stabletransit.com, dns2.stabletransit.com)
Analysis
IP Addresses
fdbk.com resolves to one IP address: 162.209.106.164.
Name Servers
The authoritative name servers for fdbk.com are ns.rackspace.com, dns1.stabletransit.com and dns2.stabletransit.com — three in total.
The name servers of fdbk.com overlap at least partially with those of other domains — among them medworks.gr, clarencevalleyseptics.com.au, 119.57.50.in-addr.arpa and two more.
These name servers commonly appear alongside the name servers ns2.rackspace.com and dns.stabletransit.com.
Each of the three hostnames — ns.rackspace.com, dns1.stabletransit.com and dns2.stabletransit.com — has a single IP address. ns.rackspace.com and dns1.stabletransit.com resolve to 69.20.95.4; dns2.stabletransit.com resolves to 65.61.188.4.
Both ns.rackspace.com and dns1.stabletransit.com resolve to 69.20.95.4 IP addresses each.
Mail Servers
Five mail servers handle fdbk.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
fdbk.com has at least partial mail server overlap with other domains such as ccswebtool.com, discoverychurch.com, thejsops.com and two more.
These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx3.googlemail.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com directs traffic to 142.251.163.26 and 2607:f8b0:4004:c1b::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1b.