silkykey.com - robtex.com
silkykey.com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| 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=1774132315 | ||||||
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=1774413007 | ||||||
Same first word
silkykey.com |
DNS History
12 records (4 active, 8 former)
○NSdns1.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs
○ 2026-03-18 09:37:58
○ 2026-03-25 04:39:28
○NSdns2.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs
○ 2026-03-18 09:37:58
○ 2026-03-25 04:39:28
●NSlaunch1.spaceship.net2026-03-18 → 2026-03-25 · 3 obs
● 2026-03-18 09:37:58
● 2026-03-25 04:39:28
●NSlaunch2.spaceship.net2026-03-18 → 2026-03-25 · 3 obs
● 2026-03-18 09:37:58
● 2026-03-25 04:39:28
○MXeforward1.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs
○ 2026-03-18 09:37:58
○ 2026-03-25 04:39:28
○MXeforward2.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs
○ 2026-03-18 09:37:58
○ 2026-03-25 04:39:28
○MXeforward3.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs
○ 2026-03-18 09:37:58
○ 2026-03-25 04:39:28
○MXeforward4.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs
○ 2026-03-18 09:37:58
○ 2026-03-25 04:39:28
○MXeforward5.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs
○ 2026-03-18 09:37:58
○ 2026-03-25 04:39:28
○A162.255.119.782019-12-15 → 2019-12-15 · 3 obs
○ 2026-03-18 09:37:58
○ 2026-03-25 04:39:28
●A44.232.173.2492026-03-18 → 2026-03-25 · 3 obs
● 2026-03-18 09:37:58
● 2026-03-25 04:39:28
●A52.40.42.1132026-03-18 → 2026-03-25 · 3 obs
● 2026-03-18 09:37:58
● 2026-03-25 04:39:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, c.gtld-servers.net, l.gtld-servers.net, a.gtld-servers.net... | - |
| silkykey.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.27.32
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 458ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 44.232.173.249, 52.40.42.113 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
The entity silkykey.com points to two IP numbers: 44.232.173.249 and 52.40.42.113.
For instance, other host names lgc.cc, feedranker.com, smeow.com, itraj.com and futurefood.us share IP numbers with silkykey.com.
Name Servers
silkykey.com is delegated to two name servers: launch1.spaceship.net and launch2.spaceship.net.
silkykey.com uses the same name server setup as other domains such as rossandrose.com, tiagomontes.com, clear-review.com, skinrestored.com and moviestar.tv.
silkykey.com shares name servers with other domains at least partially, for instance greenwavedesign.com and domainsalesdirect.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.