discoverleisure.com - robtex.com
discoverleisure.com
| 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 | ||||||
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=1784539772 | ||||||
Same first word
discoverleisure.com |
DNS History
12 records (4 active, 8 former)
○NSdns1.name-services.com2015-08-09 → 2017-03-14 · 5 obs
● 2015-08-09 13:10:40
● 2017-03-14 09:51:32
○ 2020-01-06 12:58:52
○ 2026-07-20 09:39:32
○NSdns2.name-services.com2015-08-09 → 2017-03-14 · 5 obs
● 2015-08-09 13:10:40
● 2017-03-14 09:51:32
○ 2020-01-06 12:58:52
○ 2026-07-20 09:39:32
○NSdns3.name-services.com2015-08-09 → 2017-03-14 · 5 obs
● 2015-08-09 13:10:40
● 2017-03-14 09:51:32
○ 2020-01-06 12:58:52
○ 2026-07-20 09:39:32
○NSdns4.name-services.com2015-08-09 → 2017-03-14 · 5 obs
● 2015-08-09 13:10:40
● 2017-03-14 09:51:32
○ 2020-01-06 12:58:52
○ 2026-07-20 09:39:32
○NSdns5.name-services.com2015-08-09 → 2017-03-14 · 5 obs
● 2015-08-09 13:10:40
● 2017-03-14 09:51:32
○ 2020-01-06 12:58:52
○ 2026-07-20 09:39:32
●NSns1.namefind.com2020-01-06 → 2026-07-20 · 3 obs
● 2020-01-06 12:58:52
● 2026-07-20 09:39:32
●NSns2.namefind.com2020-01-06 → 2026-07-20 · 3 obs
● 2020-01-06 12:58:52
● 2026-07-20 09:39:32
●A13.248.169.482026-06-16 → 2026-07-20 · 3 obs
● 2026-06-16 22:13:50
● 2026-07-20 09:39:32
○A209.62.20.1752008-03-18 → 2008-03-18 · 3 obs
○ 2015-08-09 13:10:40
○ 2026-07-20 09:39:32
○A35.186.238.1012020-01-06 → 2020-01-06 · 4 obs
● 2020-01-06 12:58:52
○ 2026-06-16 22:13:50
○ 2026-07-20 09:39:32
○A69.64.147.2492015-08-09 → 2017-03-14 · 5 obs
● 2015-08-09 13:10:40
● 2017-03-14 09:51:32
○ 2020-01-06 12:58:52
○ 2026-07-20 09:39:32
●A76.223.54.1462026-06-16 → 2026-07-20 · 3 obs
● 2026-06-16 22:13:50
● 2026-07-20 09:39:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| discoverleisure.com | ns2.namefind.com, ns1.namefind.com | 2 records |
✅ Authoritative Response
Server:97.74.99.64
NS records: ns2.namefind.com, ns1.namefind.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for discoverleisure.com (unsigned zone)
⏱️ Timing
Total: 154ms | 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 |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns2.namefind.com, ns1.namefind.com)
Analysis
IP Addresses
discoverleisure.com directs to two IP numbers, 13.248.169.48 and 76.223.54.146
Additional host names — mango4.com, mail.hellopasadena.com, darkorbit.oyun.(0x736578)roulette.allt.com and two others — share IP numbers with discoverleisure.com.
Name Servers
discoverleisure.com is served by two delegated name servers, ns1.namefind.com and ns2.namefind.com.
discoverleisure.com shares its name server setup with other domains, including testexample.com, nullmx.vick.org, vermontpawn.com and two others.
The DNS delegation for discoverleisure.com at least partly coincides with that of other domains, fba.us being one example.
ns1.namefind.com and ns2.namefind.com each resolve to one IP number: ns1.namefind.com points to 97.74.99.64 and ns2.namefind.com points to 173.201.67.64.