futurefanbase.com - dns.ninja
futurefanbase.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=1783203516 | ||||||
Same first word
futurefanbase.com |
DNS History
8 records (8 active, 0 former)
●MXalt1.aspmx.l.google.com2017-05-12 → 2026-07-04 · 2 obs
● 2026-07-04 22:48:16
●MXalt2.aspmx.l.google.com2017-05-12 → 2026-07-04 · 2 obs
● 2026-07-04 22:48:16
●MXalt3.aspmx.l.google.com2017-05-12 → 2026-07-04 · 2 obs
● 2026-07-04 22:48:16
●MXalt4.aspmx.l.google.com2017-05-12 → 2026-07-04 · 2 obs
● 2026-07-04 22:48:16
●MXaspmx.l.google.com2017-05-12 → 2026-07-04 · 2 obs
● 2026-07-04 22:48:16
●A37.139.14.2082017-05-12 → 2026-07-04 · 2 obs
● 2026-07-04 22:48:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| futurefanbase.com | ns1.hover.com, ns2.hover.com | 4 records |
✅ Authoritative Response
Server:216.40.47.26
NS records: ns1.hover.com, ns2.hover.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for futurefanbase.com (unsigned zone)
⏱️ Timing
Total: 246ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 37.139.14.208 |
| NS | 2 | ns1.hover.com, ns2.hover.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | google-site-verification=Hv-S9n2ENf-Lmue |
| SOA | 1 | ns1.hover.com dnsmaster.hover.com |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.hover.com, ns1.hover.com, ns2.hover.com...)
Analysis
IP Addresses
futurefanbase.com has exactly one IP address — 37.139.14.208.
Name Servers
DNS delegation for futurefanbase.com points to two name servers: ns1.hover.com and ns2.hover.com.
The name server configuration of futurefanbase.com is shared with other domains, for instance bicycletoolsdirect.com, oandco.us, kttp.com and two others.
At least some of futurefanbase.com's name servers are shared with other domains, for example linterm.net, mailadouche.com, wikiasearch.net and two more.
These name servers are often deployed together with the name servers ns3.hover.com, ns1.domaindirect.com, ns2.domaindirect.com and ns3.domaindirect.com.
ns1.hover.com directs to 216.40.47.26 and 2604:4000:0:d:216:40:47:26. ns2.hover.com directs to 64.98.148.13 and 2604:4000:2800:d:64:99:148:13. Each host name carries two IP addresses.
Mail Servers
futurefanbase.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by futurefanbase.com are shared with other domains: etuetu.com, hendore.com, ideaware.co.kr and two others among them.
These mail servers often appear in conjunction with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.
Host names pointing to two IP addresses:
aspmx.l.google.com has two IP addresses: 172.253.115.26 and 2607:f8b0:4004:c21::1a.
alt1.aspmx.l.google.com has two IP addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com has two IP addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com has two IP addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com has two IP addresses: 172.253.157.27 and 2a00:1450:400c:c23::1a.