fflsafe.com - dns.ninja
fflsafe.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=1785344447 | ||||||
Subdomains
staging.fflsafe.com |
Same first word
fflsafe.com |
DNS History
12 records (8 active, 4 former)
●NSjavon.ns.cloudflare.com2026-03-12 → 2026-07-29 · 3 obs
● 2026-03-12 07:51:36
● 2026-07-29 17:23:42
○NSns-cloud-d1.googledomains.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-12 07:51:36
○ 2026-07-29 17:23:42
○NSns-cloud-d2.googledomains.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-12 07:51:36
○ 2026-07-29 17:23:42
○NSns-cloud-d3.googledomains.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-12 07:51:36
○ 2026-07-29 17:23:42
○NSns-cloud-d4.googledomains.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-12 07:51:36
○ 2026-07-29 17:23:42
●NSshubhi.ns.cloudflare.com2026-03-12 → 2026-07-29 · 3 obs
● 2026-03-12 07:51:36
● 2026-07-29 17:23:42
●MXalt1.aspmx.l.google.com2026-03-12 → 2026-07-29 · 2 obs
● 2026-07-29 17:23:42
●MXalt2.aspmx.l.google.com2026-03-12 → 2026-07-29 · 2 obs
● 2026-07-29 17:23:42
●MXalt3.aspmx.l.google.com2026-03-12 → 2026-07-29 · 2 obs
● 2026-07-29 17:23:42
●MXalt4.aspmx.l.google.com2026-03-12 → 2026-07-29 · 2 obs
● 2026-07-29 17:23:42
●MXaspmx.l.google.com2026-03-12 → 2026-07-29 · 2 obs
● 2026-07-29 17:23:42
●A34.174.254.2092026-03-12 → 2026-07-29 · 2 obs
● 2026-07-29 17:23:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, i.gtld-servers.net, k.gtld-servers.net, c.gtld-servers.net... | - |
| fflsafe.com | shubhi.ns.cloudflare.com, javon.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.194.63
NS records: shubhi.ns.cloudflare.com, javon.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fflsafe.com (unsigned zone)
⏱️ Timing
Total: 200ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 34.174.254.209 |
| NS | 2 | javon.ns.cloudflare.com, shubhi.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | v=spf1 a mx include:_spf.elasticemail.co, v=spf1 include:_spf.google.com ~all |
| SOA | 1 | javon.ns.cloudflare.com dns.cloudflare.c |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (shubhi.ns.cloudflare.com, shubhi.ns.cloudflare.com, shubhi.ns.cloudflare.com...)
Analysis
Hierarchy
The domain staging.fflsafe.com falls under the parent fflsafe.com.
IP Addresses
fflsafe.com points to a single IP number: 34.174.254.209.
Additional host names — vatracie.com, marrecife.com, autodestruct.com and two others — share IP numbers with fflsafe.com.
Name Servers
fflsafe.com is delegated to two name servers: javon.ns.cloudflare.com and shubhi.ns.cloudflare.com.
fflsafe.com shares its name server setup with other domains, including fwom.org, toir-m.ru, ggbetschweiz.com and two others.
At least some of fflsafe.com's name servers are shared with other domains, for example smeg.co.nz, rediscoveringu.org, tyfauto.com and two more.
These name servers are often deployed together with the name servers hank.ns.cloudflare.com, pearl.ns.cloudflare.com, newt.ns.cloudflare.com and ziggy.ns.cloudflare.com.
Host names with 6 IP numbers:
javon.ns.cloudflare.com resolves to 108.162.195.108, 162.159.44.108, 172.64.35.108 and 3 other IP addresses.
shubhi.ns.cloudflare.com resolves to 108.162.194.63, 162.159.38.63, 172.64.34.63 and 3 other IP addresses.
Mail Servers
Five mail servers handle fflsafe.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
fflsafe.com shares mail servers — at least in part — with other domains, including ns500731.ns500731.ns500671.ns500754.ns500754.ns500742.ns500671.ns500688.ns500704.ns500678.ns500291.ns500291.ns500131.lustychickser.com, ns500699.ns500699.ns500699.ns500699.ns500693.ns500693.ns500734.ns500693.ns500734.ns500693.ns500683.ns500683.ns500693.ns500683.ns500683.ns500699.ns500602.dtrkdll.com, ns500759.ns500698.ns500758.ns500758.ns500735.ns500735.ns500736.ns500735.ns500735.ns500576.ns500576.ns500698.ns500686.ns500686.ns500576.ns500619.trackreceptor.com and two others.
These mail servers are frequently paired with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx3.googlemail.com and aspmx2.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to 142.251.163.26 and 2607:f8b0:4004:c23::1a.
alt1.aspmx.l.google.com points to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com points to 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com points to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com points to 172.253.157.27 and 2a00:1450:400c:c23::1b.