chainsafety.com - dns.ninja
chainsafety.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 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1780767462 | ||||||
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=1783210741 | ||||||
Same first word
chainsafety.com |
Similar names
safetychain.nl |
safetychain.co |
chinasafety.net |
safetychain.net |
chinasafety.com.cn |
chinasafety.ac.cn |
safetychain.com |
DNS History
12 records (4 active, 8 former)
●NSlaunch1.spaceship.net2026-06-09 → 2026-07-05 · 3 obs
● 2026-06-09 14:45:14
● 2026-07-05 00:48:40
●NSlaunch2.spaceship.net2026-06-09 → 2026-07-05 · 3 obs
● 2026-06-09 14:45:14
● 2026-07-05 00:48:40
○NSns1.uniregistrymarket.link2018-08-26 → 2018-08-26 · 3 obs
○ 2026-06-09 14:45:14
○ 2026-07-05 00:48:40
○NSns2.uniregistrymarket.link2018-08-26 → 2018-08-26 · 3 obs
○ 2026-06-09 14:45:14
○ 2026-07-05 00:48:40
○MXmx1-forward.atom.com2026-06-09 → 2026-07-05 · 2 obs
○ 2026-07-05 00:48:40
○MXmx2-forward.atom.com2026-06-09 → 2026-07-05 · 2 obs
○ 2026-07-05 00:48:40
●A44.232.173.2492026-06-09 → 2026-07-05 · 3 obs
● 2026-06-09 14:45:14
● 2026-07-05 00:48:40
○A52.20.84.622026-06-09 → 2026-07-05 · 2 obs
○ 2026-07-05 00:48:40
●A52.40.42.1132026-06-09 → 2026-07-05 · 3 obs
● 2026-06-09 14:45:14
● 2026-07-05 00:48:40
○A69.172.201.1532018-08-26 → 2018-08-26 · 3 obs
○ 2026-06-09 14:45:14
○ 2026-07-05 00:48:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, d.gtld-servers.net, g.gtld-servers.net, b.gtld-servers.net... | - |
| chainsafety.com | ns1.atom.com, ns2.atom.com | 2 records |
✅ Authoritative Response
Server:44.219.81.145
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for chainsafety.com (unsigned zone)
⏱️ Timing
Total: 3695ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns1.atom.com, ns2.atom.com |
| MX | 2 | mx2-forward.atom.com (pri: 10), mx1-forward.atom.com (pri: 10) |
| SOA | 1 | ns1.atom.com hostmaster.chainsafety.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
chainsafety.com has two IP addresses: 44.232.173.249 and 52.40.42.113
fmclima.com, rhodesianridgeback.net, mymotto.com and two other host names share IP numbers with chainsafety.com.
Name Servers
chainsafety.com uses two name servers for its delegation: launch1.spaceship.net and launch2.spaceship.net.
chainsafety.com uses the same name servers as several other domains — among them direct-topup.com, steppeai.com, mensclub.xyz and two more.
chainsafety.com has overlapping name servers with several other domains — among them silver007.com, easyai.com, airino.com and shepherdwatch.com.
These name servers commonly appear alongside the name servers ns1.afternic.com and ns2.afternic.com.
The two host names launch1.spaceship.net and launch2.spaceship.net each have a pair of IP addresses: launch1.spaceship.net has 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26, and launch2.spaceship.net has 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.