cross-fix.com - dns.ninja
cross-fix.com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| A | 44.233.250.75🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix | ||||||
| PTR | ec2-44-233-250-75.us-west-2.compute.amazonaws.com | ||||||
| A | 52.38.196.63🇺🇸 Amazon52.36.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 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1783358285 | ||||||
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=1783706262 | ||||||
Previously MX for
cross-fix.com |
Same first word
cross-fix.com |
DNS History
15 records (4 active, 11 former)
○NSdns20.ovh.net2020-03-15 → 2020-03-15 · 4 obs
○ 2016-09-10 11:44:06
● 2020-03-15 04:34:36
○ 2026-05-14 15:16:04
○ 2026-07-10 18:20:14
● 2020-03-15 04:34:36
○ 2026-05-14 15:16:04
○ 2026-07-10 18:20:14
●NSlaunch1.spaceship.net2026-05-14 → 2026-07-10 · 3 obs
○ 2020-03-15 04:34:36
● 2026-05-14 15:16:04
● 2026-07-10 18:20:14
● 2026-05-14 15:16:04
● 2026-07-10 18:20:14
●NSlaunch2.spaceship.net2026-05-14 → 2026-07-10 · 3 obs
○ 2020-03-15 04:34:36
● 2026-05-14 15:16:04
● 2026-07-10 18:20:14
● 2026-05-14 15:16:04
● 2026-07-10 18:20:14
○NSmaster.dns.ne.jp2015-06-09 → 2016-04-04 · 4 obs
● 2015-06-09 19:00:12
● 2016-04-04 17:02:20
○ 2016-09-10 11:44:06
○ 2026-07-10 18:20:14
● 2016-04-04 17:02:20
○ 2016-09-10 11:44:06
○ 2026-07-10 18:20:14
○NSns1.dns.ne.jp2015-06-09 → 2016-04-04 · 4 obs
● 2015-06-09 19:00:12
● 2016-04-04 17:02:20
○ 2016-09-10 11:44:06
○ 2026-07-10 18:20:14
● 2016-04-04 17:02:20
○ 2016-09-10 11:44:06
○ 2026-07-10 18:20:14
○NSns2.dns.ne.jp2015-06-09 → 2016-04-04 · 4 obs
● 2015-06-09 19:00:12
● 2016-04-04 17:02:20
○ 2016-09-10 11:44:06
○ 2026-07-10 18:20:14
● 2016-04-04 17:02:20
○ 2016-09-10 11:44:06
○ 2026-07-10 18:20:14
○NSns20.ovh.net2020-03-15 → 2020-03-15 · 4 obs
○ 2016-09-10 11:44:06
● 2020-03-15 04:34:36
○ 2026-05-14 15:16:04
○ 2026-07-10 18:20:14
● 2020-03-15 04:34:36
○ 2026-05-14 15:16:04
○ 2026-07-10 18:20:14
○MXcross-fix.com2015-06-09 → 2016-04-04 · 4 obs
● 2015-06-09 19:00:12
● 2016-04-04 17:02:20
○ 2016-09-10 11:44:06
○ 2026-07-10 18:20:14
● 2016-04-04 17:02:20
○ 2016-09-10 11:44:06
○ 2026-07-10 18:20:14
○MXredirect.ovh.net2020-03-15 → 2020-03-15 · 4 obs
○ 2016-09-10 11:44:06
● 2020-03-15 04:34:36
○ 2026-05-14 15:16:04
○ 2026-07-10 18:20:14
● 2020-03-15 04:34:36
○ 2026-05-14 15:16:04
○ 2026-07-10 18:20:14
○A219.94.128.1512015-06-09 → 2016-04-04 · 4 obs
● 2015-06-09 19:00:12
● 2016-04-04 17:02:20
○ 2016-09-10 11:44:06
○ 2026-07-10 18:20:14
● 2016-04-04 17:02:20
○ 2016-09-10 11:44:06
○ 2026-07-10 18:20:14
○A44.232.173.2492026-05-14 → 2026-05-14 · 4 obs
○ 2020-03-15 04:34:36
● 2026-05-14 15:16:04
○ 2026-07-10 18:20:12
○ 2026-07-10 18:20:14
● 2026-05-14 15:16:04
○ 2026-07-10 18:20:12
○ 2026-07-10 18:20:14
●A44.233.250.752026-07-10 → 2026-07-10 · 3 obs
○ 2026-05-14 15:16:04
● 2026-07-10 18:20:12
● 2026-07-10 18:20:14
● 2026-07-10 18:20:12
● 2026-07-10 18:20:14
●A52.38.196.632026-07-10 → 2026-07-10 · 3 obs
○ 2026-05-14 15:16:04
● 2026-07-10 18:20:12
● 2026-07-10 18:20:14
● 2026-07-10 18:20:12
● 2026-07-10 18:20:14
○A52.40.42.1132026-05-14 → 2026-05-14 · 4 obs
○ 2020-03-15 04:34:36
● 2026-05-14 15:16:04
○ 2026-07-10 18:20:12
○ 2026-07-10 18:20:14
● 2026-05-14 15:16:04
○ 2026-07-10 18:20:12
○ 2026-07-10 18:20:14
○A87.98.235.1842020-03-15 → 2020-03-15 · 4 obs
○ 2016-09-10 11:44:06
● 2020-03-15 04:34:36
○ 2026-05-14 15:16:04
○ 2026-07-10 18:20:14
● 2020-03-15 04:34:36
○ 2026-05-14 15:16:04
○ 2026-07-10 18:20:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| cross-fix.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.26.38
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
❌ Bogus (DNSSEC validation failed)
No DNSKEY for cross-fix.com
⏱️ Timing
Total: 1219ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.38.196.63, 44.233.250.75 |
| NS | 2 | launch1.spaceship.net, launch2.spaceship.net |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
cross-fix.com resolves to the IP addresses 44.233.250.75 and 52.38.196.63
adlinkia.com, arue.top, casasdelasubbetica.com plus two other host names have IP numbers in common with cross-fix.com.
Name Servers
The NS records for cross-fix.com delegate to launch1.spaceship.net and launch2.spaceship.net.
The name server configuration of cross-fix.com is shared with other domains, for instance mirageengine.com, elprimer.com, cityofolivehillutilities.com and two others.
launch1.spaceship.net resolves to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26. Likewise, launch2.spaceship.net resolves to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20 — two IP addresses apiece.