finalprotocol.com - robtex.com

finalprotocol.com

DNSSEC⚠️ Not signed
A44.232.173.249🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix
PTRec2-44-232-173-249.us-west-2.compute.amazonaws.com
A52.40.42.113🇺🇸 Amazon52.40.0.0/14 EC2 PDX prefix
NSlaunch1.spaceship.net ⭐
A2400:cb00:2049:1::a29f:1a26🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street
A162.159.26.38Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRip-162-159-26-38.defastlink.net
NSlaunch2.spaceship.net
A2400:cb00:2049:1::a29f:1b20🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street
A162.159.27.32Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRip-162-159-27-32.defastlink.net
TXTbb13bdd2-b9ae-480a-8a9e-6d78b4fc9417
SOAlaunch1.spaceship.netsupport@spaceship.com serial=1769496060

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1771291435

Previously MX for

finalprotocol.com

Same first word

finalprotocol.com

DNS History

20 records (4 active, 16 former)

20162017201820192020202120222023202420252026NSlaunch1.spaceship.netlaunch2.spaceship.netns1.clearsdn.comns1.mydyndns.orgns1177.dns.dyn.comns2.clearsdn.comns2139.dns.dyn.comns3.clearsdn.comns3166.dns.dyn.comns4.clearsdn.comns4161.dns.dyn.comMXfinalprotocol.commxbackup1.clearsdn.commxbackup2.clearsdn.comraymondo.orgA44.232.173.24952.40.42.11350.91.183.19665.33.78.84CNAMEraymondo.org
●NSlaunch1.spaceship.net2026-03-14 → 2026-03-19 · 3 obs
○ 2019-12-29 01:39:20
● 2026-03-14 10:59:34
● 2026-03-19 14:26:50
●NSlaunch2.spaceship.net2026-03-14 → 2026-03-19 · 3 obs
○ 2019-12-29 01:39:20
● 2026-03-14 10:59:34
● 2026-03-19 14:26:50
○NSns1.clearsdn.com2015-08-13 → 2017-03-21 · 4 obs
● 2015-08-13 22:58:14
● 2017-03-21 11:48:24
○ 2019-12-29 01:39:20
○ 2026-03-19 14:26:50
○NSns1.mydyndns.org2019-12-29 → 2019-12-29 · 4 obs
○ 2017-03-21 11:48:24
● 2019-12-29 01:39:20
○ 2026-03-14 10:59:34
○ 2026-03-19 14:26:50
○NSns1177.dns.dyn.com2019-12-29 → 2019-12-29 · 4 obs
○ 2017-03-21 11:48:24
● 2019-12-29 01:39:20
○ 2026-03-14 10:59:34
○ 2026-03-19 14:26:50
○NSns2.clearsdn.com2015-08-13 → 2017-03-21 · 4 obs
● 2015-08-13 22:58:14
● 2017-03-21 11:48:24
○ 2019-12-29 01:39:20
○ 2026-03-19 14:26:50
○NSns2139.dns.dyn.com2019-12-29 → 2019-12-29 · 4 obs
○ 2017-03-21 11:48:24
● 2019-12-29 01:39:20
○ 2026-03-14 10:59:34
○ 2026-03-19 14:26:50
○NSns3.clearsdn.com2015-08-13 → 2017-03-21 · 4 obs
● 2015-08-13 22:58:14
● 2017-03-21 11:48:24
○ 2019-12-29 01:39:20
○ 2026-03-19 14:26:50
○NSns3166.dns.dyn.com2019-12-29 → 2019-12-29 · 4 obs
○ 2017-03-21 11:48:24
● 2019-12-29 01:39:20
○ 2026-03-14 10:59:34
○ 2026-03-19 14:26:50
○NSns4.clearsdn.com2015-08-13 → 2017-03-21 · 4 obs
● 2015-08-13 22:58:14
● 2017-03-21 11:48:24
○ 2019-12-29 01:39:20
○ 2026-03-19 14:26:50
○NSns4161.dns.dyn.com2019-12-29 → 2019-12-29 · 4 obs
○ 2017-03-21 11:48:24
● 2019-12-29 01:39:20
○ 2026-03-14 10:59:34
○ 2026-03-19 14:26:50
○MXfinalprotocol.com2019-12-29 → 2019-12-29 · 4 obs
○ 2017-03-21 11:48:24
● 2019-12-29 01:39:20
○ 2026-03-14 10:59:34
○ 2026-03-19 14:26:50
○MXmxbackup1.clearsdn.com2015-12-07 → 2017-03-21 · 4 obs
● 2015-12-07 19:16:48
● 2017-03-21 11:48:24
○ 2019-12-29 01:39:20
○ 2026-03-19 14:26:50
○MXmxbackup2.clearsdn.com2015-12-07 → 2017-03-21 · 4 obs
● 2015-12-07 19:16:48
● 2017-03-21 11:48:24
○ 2019-12-29 01:39:20
○ 2026-03-19 14:26:50
○MXraymondo.org2015-12-07 → 2017-03-21 · 4 obs
● 2015-12-07 19:16:48
● 2017-03-21 11:48:24
○ 2019-12-29 01:39:20
○ 2026-03-19 14:26:50
●A44.232.173.2492026-03-14 → 2026-03-19 · 3 obs
○ 2019-12-29 01:39:20
● 2026-03-14 10:59:34
● 2026-03-19 14:26:50
○A50.91.183.1962019-12-29 → 2019-12-29 · 4 obs
○ 2017-03-21 11:48:24
● 2019-12-29 01:39:20
○ 2026-03-14 10:59:34
○ 2026-03-19 14:26:50
●A52.40.42.1132026-03-14 → 2026-03-19 · 3 obs
○ 2019-12-29 01:39:20
● 2026-03-14 10:59:34
● 2026-03-19 14:26:50
○A65.33.78.842015-08-13 → 2017-03-21 · 4 obs
● 2015-08-13 22:58:14
● 2017-03-21 11:48:24
○ 2019-12-29 01:39:20
○ 2026-03-19 14:26:50
○CNAMEraymondo.org2015-08-13 → 2017-03-21 · 4 obs
● 2015-08-13 22:58:14
● 2017-03-21 11:48:24
○ 2019-12-29 01:39:20
○ 2026-03-19 14:26:50

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
finalprotocol.comlaunch2.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 finalprotocol.com (unsigned zone)

⏱️ Timing

Total: 976ms | Queries: -

📄 Records

TypeCountSample Data
A244.232.173.249, 52.40.42.113
NS2launch1.spaceship.net, launch2.spaceship.net
TXT1bb13bdd2-b9ae-480a-8a9e-6d78b4fc9417
SOA1launch1.spaceship.net support.spaceship.

Analysis

IP Addresses

finalprotocol.com resolves to two IP numbers: 44.232.173.249 and 52.40.42.113.

Other host names, for instance shotverse.com, butterfly.asia, quantaw.com, mdsa.co.uk and follow.asia share IP numbers with finalprotocol.com.

Name Servers

Two name servers launch1.spaceship.net and launch2.spaceship.net handle delegation for finalprotocol.com.

finalprotocol.com uses the same name server setup as other domains, for example (0x787878)mir.info, 58.at, pppp.mobi, myaibox.com and elitebody.co.uk.

finalprotocol.com partially shares name servers with other domains, such as canidata.com and mojlan.com.

Host names with two IP numbers:

launch1.spaceship.net points to: 2400:cb00:2049:1::a29f:1a26 and 162.159.26.38

launch2.spaceship.net points to: 2400:cb00:2049:1::a29f:1b20 and 162.159.27.32