findingflorida.com - robtex.com
findingflorida.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 44.232.173.249🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix | ||||||
| PTR | ec2-44-232-173-249.us-west-2.compute.amazonaws.com | ||||||
| A | 52.40.42.113🇺🇸 Amazon52.40.0.0/14 EC2 PDX prefix | ||||||
| NS | launch1.spaceship.net ⭐ | ||||||
| A | 2400:cb00:2049:1::a29f:1a26🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.38Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | launch2.spaceship.net | ||||||
| A | 2400:cb00:2049:1::a29f:1b20🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.27.32Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| TXT | 76a74d6e-db1e-4bce-953f-033ce2f733db | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1774803617 | ||||||
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=1776060412 | ||||||
Same first word
findingflorida.com |
findingflorida.org |
DNS History
15 records (4 active, 11 former)
○NSbuy.internettraffic.com2015-06-02 → 2015-06-02 · 3 obs
● 2015-06-02 18:28:00
○ 2015-10-17 11:30:58
○ 2026-04-13 06:10:06
○ 2015-10-17 11:30:58
○ 2026-04-13 06:10:06
●NSlaunch1.spaceship.net2026-04-10 → 2026-04-13 · 3 obs
○ 2017-02-18 10:13:32
● 2026-04-10 19:52:06
● 2026-04-13 06:10:06
● 2026-04-10 19:52:06
● 2026-04-13 06:10:06
●NSlaunch2.spaceship.net2026-04-10 → 2026-04-13 · 3 obs
○ 2017-02-18 10:13:32
● 2026-04-10 19:52:06
● 2026-04-13 06:10:06
● 2026-04-10 19:52:06
● 2026-04-13 06:10:06
○NSns1.sedoparking.com2015-10-17 → 2016-06-17 · 5 obs
○ 2015-06-02 18:28:00
● 2015-10-17 11:30:58
● 2016-06-17 18:35:10
○ 2017-02-18 10:13:32
○ 2026-04-13 06:10:06
● 2015-10-17 11:30:58
● 2016-06-17 18:35:10
○ 2017-02-18 10:13:32
○ 2026-04-13 06:10:06
○NSns1.uniregistrymarket.link2017-02-18 → 2017-02-18 · 4 obs
○ 2016-06-17 18:35:10
● 2017-02-18 10:13:32
○ 2026-04-10 19:52:06
○ 2026-04-13 06:10:06
● 2017-02-18 10:13:32
○ 2026-04-10 19:52:06
○ 2026-04-13 06:10:06
○NSns2.sedoparking.com2015-10-17 → 2016-06-17 · 5 obs
○ 2015-06-02 18:28:00
● 2015-10-17 11:30:58
● 2016-06-17 18:35:10
○ 2017-02-18 10:13:32
○ 2026-04-13 06:10:06
● 2015-10-17 11:30:58
● 2016-06-17 18:35:10
○ 2017-02-18 10:13:32
○ 2026-04-13 06:10:06
○NSns2.uniregistrymarket.link2017-02-18 → 2017-02-18 · 4 obs
○ 2016-06-17 18:35:10
● 2017-02-18 10:13:32
○ 2026-04-10 19:52:06
○ 2026-04-13 06:10:06
● 2017-02-18 10:13:32
○ 2026-04-10 19:52:06
○ 2026-04-13 06:10:06
○NSsell.internettraffic.com2015-06-02 → 2015-06-02 · 3 obs
● 2015-06-02 18:28:00
○ 2015-10-17 11:30:58
○ 2026-04-13 06:10:06
○ 2015-10-17 11:30:58
○ 2026-04-13 06:10:06
○MXmail.nickstel.com2015-10-17 → 2016-06-17 · 4 obs
● 2015-10-17 11:30:58
● 2016-06-17 18:35:10
○ 2017-02-18 10:13:32
○ 2026-04-13 06:10:06
● 2016-06-17 18:35:10
○ 2017-02-18 10:13:32
○ 2026-04-13 06:10:06
○A162.243.47.2142019-12-26 → 2019-12-26 · 4 obs
○ 2017-02-18 10:13:32
● 2019-12-26 08:19:06
○ 2026-04-10 19:52:06
○ 2026-04-13 06:10:06
● 2019-12-26 08:19:06
○ 2026-04-10 19:52:06
○ 2026-04-13 06:10:06
●A44.232.173.2492026-04-10 → 2026-04-13 · 3 obs
○ 2019-12-26 08:19:06
● 2026-04-10 19:52:06
● 2026-04-13 06:10:06
● 2026-04-10 19:52:06
● 2026-04-13 06:10:06
●A52.40.42.1132026-04-10 → 2026-04-13 · 3 obs
○ 2019-12-26 08:19:06
● 2026-04-10 19:52:06
● 2026-04-13 06:10:06
● 2026-04-10 19:52:06
● 2026-04-13 06:10:06
○A69.172.201.1532017-02-18 → 2017-02-18 · 4 obs
○ 2016-06-17 18:35:10
● 2017-02-18 10:13:32
○ 2019-12-26 08:19:06
○ 2026-04-13 06:10:06
● 2017-02-18 10:13:32
○ 2019-12-26 08:19:06
○ 2026-04-13 06:10:06
○A69.172.201.2082015-06-02 → 2015-06-02 · 3 obs
● 2015-06-02 18:28:00
○ 2015-10-17 11:30:58
○ 2026-04-13 06:10:06
○ 2015-10-17 11:30:58
○ 2026-04-13 06:10:06
○A72.52.4.1202015-10-17 → 2016-06-17 · 5 obs
○ 2015-06-02 18:28:00
● 2015-10-17 11:30:58
● 2016-06-17 18:35:10
○ 2017-02-18 10:13:32
○ 2026-04-13 06:10:06
● 2015-10-17 11:30:58
● 2016-06-17 18:35:10
○ 2017-02-18 10:13:32
○ 2026-04-13 06:10:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| findingflorida.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.26.38
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for findingflorida.com (unsigned zone)
⏱️ Timing
Total: 894ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 44.232.173.249, 52.40.42.113 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 1 | 76a74d6e-db1e-4bce-953f-033ce2f733db |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
findingflorida.com points to two IP numbers: 44.232.173.249 and 52.40.42.113.
Other host names, for instance dqhm.com, fitmag.co.uk, fpc.us, pubest.com and catshop.ca share IP numbers with findingflorida.com.
Name Servers
findingflorida.com is delegated to two name servers: launch1.spaceship.net and launch2.spaceship.net.
findingflorida.com uses the same name server setup as other domains, for instance icmda.com, astridjacobsen.com, gazelle.co, btc.gift and semiauto.com.
Host names with two IP numbers:
The host launch1.spaceship.net points to 2400:cb00:2049:1::a29f:1a26 and 162.159.26.38.
The host launch2.spaceship.net points to 2400:cb00:2049:1::a29f:1b20 and 162.159.27.32.