gotfuturama.net - robtex.com
gotfuturama.net
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| NS | ns1.namefind.com ⭐ | ||||||
| A | 97.74.99.64🇺🇸 GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns1.namefind.com | ||||||
| NS | ns2.namefind.com | ||||||
| A | 173.201.67.64🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns2.namefind.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1.namefind.comdns@jomax.net 2023-03-15 #0 | ||||||
net
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net ⚠️ Not in parent delegation | ||||||
| NS | c.gtld-servers.net ⚠️ Not in parent delegation | ||||||
| NS | d.gtld-servers.net ⚠️ Not in parent delegation | ||||||
| NS | e.gtld-servers.net ⚠️ Not in parent delegation | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net ⚠️ Not in parent delegation | ||||||
| NS | i.gtld-servers.net ⚠️ Not in parent delegation | ||||||
| NS | j.gtld-servers.net ⚠️ Not in parent delegation | ||||||
| NS | k.gtld-servers.net ⚠️ Not in parent delegation | ||||||
| NS | l.gtld-servers.net ⚠️ Not in parent delegation | ||||||
| NS | m.gtld-servers.net ⚠️ Not in parent delegation | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1778462151 | ||||||
Same first word
gotfuturama.com |
gotfuturama.net |
DNS History
14 records (4 active, 10 former)
○NSbuy.internettraffic.com2015-07-01 → 2016-04-21 · 5 obs
○ 2007-09-28 23:39:14
● 2015-07-01 16:18:12
● 2016-04-21 03:30:50
○ 2016-12-23 04:12:02
○ 2026-05-11 01:26:02
● 2015-07-01 16:18:12
● 2016-04-21 03:30:50
○ 2016-12-23 04:12:02
○ 2026-05-11 01:26:02
○NSns1.linkz.com2007-09-28 → 2007-09-28 · 3 obs
● 2007-09-28 23:39:14
○ 2015-07-01 16:18:12
○ 2026-05-11 01:26:02
○ 2015-07-01 16:18:12
○ 2026-05-11 01:26:02
●NSns1.namefind.com2026-04-12 → 2026-05-11 · 3 obs
○ 2017-11-08 10:36:02
● 2026-04-12 03:28:08
● 2026-05-11 01:26:02
● 2026-04-12 03:28:08
● 2026-05-11 01:26:02
○NSns1.uniregistrymarket.link2016-12-23 → 2017-11-08 · 5 obs
○ 2016-04-21 03:30:50
● 2016-12-23 04:12:02
● 2017-11-08 10:36:02
○ 2026-04-12 03:28:08
○ 2026-05-11 01:26:02
● 2016-12-23 04:12:02
● 2017-11-08 10:36:02
○ 2026-04-12 03:28:08
○ 2026-05-11 01:26:02
○NSns2.linkz.com2007-09-28 → 2007-09-28 · 3 obs
● 2007-09-28 23:39:14
○ 2015-07-01 16:18:12
○ 2026-05-11 01:26:02
○ 2015-07-01 16:18:12
○ 2026-05-11 01:26:02
●NSns2.namefind.com2026-04-12 → 2026-05-11 · 3 obs
○ 2017-11-08 10:36:02
● 2026-04-12 03:28:08
● 2026-05-11 01:26:02
● 2026-04-12 03:28:08
● 2026-05-11 01:26:02
○NSns2.uniregistrymarket.link2016-12-23 → 2017-11-08 · 5 obs
○ 2016-04-21 03:30:50
● 2016-12-23 04:12:02
● 2017-11-08 10:36:02
○ 2026-04-12 03:28:08
○ 2026-05-11 01:26:02
● 2016-12-23 04:12:02
● 2017-11-08 10:36:02
○ 2026-04-12 03:28:08
○ 2026-05-11 01:26:02
○NSsell.internettraffic.com2015-07-01 → 2016-04-21 · 5 obs
○ 2007-09-28 23:39:14
● 2015-07-01 16:18:12
● 2016-04-21 03:30:50
○ 2016-12-23 04:12:02
○ 2026-05-11 01:26:02
● 2015-07-01 16:18:12
● 2016-04-21 03:30:50
○ 2016-12-23 04:12:02
○ 2026-05-11 01:26:02
●A13.248.169.482026-04-12 → 2026-05-11 · 3 obs
○ 2017-11-08 10:36:02
● 2026-04-12 03:28:08
● 2026-05-11 01:26:02
● 2026-04-12 03:28:08
● 2026-05-11 01:26:02
○A176.74.176.1872016-12-23 → 2017-11-08 · 5 obs
○ 2016-04-21 03:30:50
● 2016-12-23 04:12:02
● 2017-11-08 10:36:02
○ 2026-04-12 03:28:08
○ 2026-05-11 01:26:02
● 2016-12-23 04:12:02
● 2017-11-08 10:36:02
○ 2026-04-12 03:28:08
○ 2026-05-11 01:26:02
○A64.69.68.1412007-09-28 → 2007-09-28 · 3 obs
● 2007-09-28 23:39:14
○ 2015-07-01 16:18:12
○ 2026-05-11 01:26:02
○ 2015-07-01 16:18:12
○ 2026-05-11 01:26:02
○A69.172.201.1532016-04-21 → 2016-04-21 · 4 obs
○ 2016-02-01 13:48:58
● 2016-04-21 03:30:50
○ 2016-12-23 04:12:02
○ 2026-05-11 01:26:02
● 2016-04-21 03:30:50
○ 2016-12-23 04:12:02
○ 2026-05-11 01:26:02
○A69.172.201.2082015-07-01 → 2016-02-01 · 5 obs
○ 2007-09-28 23:39:14
● 2015-07-01 16:18:12
● 2016-02-01 13:48:58
○ 2016-04-21 03:30:50
○ 2026-05-11 01:26:02
● 2015-07-01 16:18:12
● 2016-02-01 13:48:58
○ 2016-04-21 03:30:50
○ 2026-05-11 01:26:02
●A76.223.54.1462026-04-12 → 2026-05-11 · 3 obs
○ 2017-11-08 10:36:02
● 2026-04-12 03:28:08
● 2026-05-11 01:26:02
● 2026-04-12 03:28:08
● 2026-05-11 01:26:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| gotfuturama.net | ns2.namefind.com, ns1.namefind.com | - |
✅ Authoritative Response
Server:97.74.99.64
NS records: ns2.namefind.com, ns1.namefind.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for gotfuturama.net (unsigned zone)
⏱️ Timing
Total: 252ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 13.248.169.48, 76.223.54.146 |
| NS | 2 | ns1.namefind.com, ns2.namefind.com |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.namefind.com dns.jomax.net |
Analysis
IP Addresses
The entity gotfuturama.net points to two IP numbers: 13.248.169.48 and 76.223.54.146.
For instance, other host names anissakate.net, www.64764.com, alensis.com, missandmaster.com and nullmx.amsheela.com share IP numbers with gotfuturama.net.
Name Servers
gotfuturama.net is delegated to two name servers: ns1.namefind.com and ns2.namefind.com.
gotfuturama.net uses the same name server setup as other domains such as typeaid.com, nullmx.americaneconomicreview.com, clubmb.com, allcrafts.org and wcfl.net.
Host names with one IP number:
ns1.namefind.com points to: 97.74.99.64.
ns2.namefind.com points to: 173.201.67.64.