futuregin.com - dns.ninja
futuregin.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=1785300302 | ||||||
Same first word
futuregin.com |
DNS History
18 records (11 active, 7 former)
●NSns41.domaincontrol.com2017-12-07 → 2026-07-29 · 2 obs
● 2026-07-29 04:49:04
●NSns42.domaincontrol.com2017-12-07 → 2026-07-29 · 2 obs
● 2026-07-29 04:49:04
●MXalt1.aspmx.l.google.com2026-07-29 → 2026-07-29 · 1 obs
●MXalt2.aspmx.l.google.com2026-07-29 → 2026-07-29 · 1 obs
●MXaspmx.l.google.com2026-07-29 → 2026-07-29 · 1 obs
●MXaspmx2.googlemail.com2026-07-29 → 2026-07-29 · 1 obs
●MXaspmx3.googlemail.com2026-07-29 → 2026-07-29 · 1 obs
○A184.168.221.452017-12-07 → 2017-12-07 · 2 obs
○ 2026-07-29 04:49:04
○A184.168.221.502017-12-07 → 2017-12-07 · 2 obs
○ 2026-07-29 04:49:04
●A198.185.159.1442026-07-29 → 2026-07-29 · 2 obs
● 2026-07-29 04:49:04
●A198.185.159.1452026-07-29 → 2026-07-29 · 2 obs
● 2026-07-29 04:49:04
●A198.49.23.1442026-07-29 → 2026-07-29 · 2 obs
● 2026-07-29 04:49:04
●A198.49.23.1452026-07-29 → 2026-07-29 · 2 obs
● 2026-07-29 04:49:04
○A50.63.202.322017-12-07 → 2017-12-07 · 2 obs
○ 2026-07-29 04:49:04
○A50.63.202.392017-12-07 → 2017-12-07 · 2 obs
○ 2026-07-29 04:49:04
○A50.63.202.482017-12-07 → 2017-12-07 · 2 obs
○ 2026-07-29 04:49:04
○A50.63.202.582017-12-07 → 2017-12-07 · 2 obs
○ 2026-07-29 04:49:04
○A50.63.202.592017-12-07 → 2017-12-07 · 2 obs
○ 2026-07-29 04:49:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, m.gtld-servers.net, b.gtld-servers.net, g.gtld-servers.net... | - |
| futuregin.com | ns41.domaincontrol.com, ns42.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.100.21
NS records: ns41.domaincontrol.com, ns42.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for futuregin.com (unsigned zone)
⏱️ Timing
Total: 351ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 198.185.159.144, 198.185.159.145... |
| NS | 2 | ns41.domaincontrol.com, ns42.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=wbVV6FRB1wHSpyW, v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns41.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns41.domaincontrol.com, ns41.domaincontrol.com, ns42.domaincontrol.com...)
Analysis
IP Addresses
futuregin.com resolves to four IP addresses: 198.49.23.144, 198.49.23.145, 198.185.159.144 and 198.185.159.145.
derrickhsiao.com, grillandpicnic.com, huntymagazine.com plus two other host names have IP numbers in common with futuregin.com.
Name Servers
futuregin.com uses two name servers for its delegation: ns41.domaincontrol.com and ns42.domaincontrol.com.
The name server configuration of futuregin.com is shared with other domains, for instance zaskitchen.com, 131f9a5aaca5.top, ezfindersfee.com and two others.
At least some of futuregin.com's name servers are also used by other domains, among them colcopy.com.
The two host names ns41.domaincontrol.com and ns42.domaincontrol.com each have a pair of IP addresses: ns41.domaincontrol.com has 97.74.100.21 and 2603:5:2142::15, and ns42.domaincontrol.com has 173.201.68.21 and 2603:5:2242::15.
Mail Servers
futuregin.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
At least some of the mail servers used by futuregin.com are shared with other domains: ns500742.ns500671.ns500742.ns500671.ns500704.ns500688.ns500705.ns500704.ns500671.ns500649.ns500131.lustychickser.com, ns500754.ns500742.ns500731.ns500754.ns500731.ns500705.ns500671.ns500291.ns500291.ns500666.ns500291.ns500291.ns500131.lustychickser.com, ns500759.ns500758.ns500758.ns500736.ns500736.ns500736.ns500735.ns500735.ns500708.ns500708.ns500708.ns500698.ns500698.ns500619.ns500686.ns500619.ns500619.trackreceptor.com and two others among them.
These mail servers are often deployed together with alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt4.aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 172.253.115.27 and 2607:f8b0:4004:c1b::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.26 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.