pacifictelegraph.com - robtex.com
pacifictelegraph.com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| 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 | 9e3321bd9bb793ae70971720020ba42b9b731ed6 | ||||||
| TXT | e567a8f9fa887e43facb77ee53ab0e9074333b12 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1785161721 | ||||||
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=1786268894 | ||||||
Same first word
pacifictelegraph.com |
DNS History
14 records (2 active, 12 former)
●NSlaunch1.spaceship.net2026-06-13 → 2026-08-09 · 3 obs
○ 2026-02-15 19:38:50
● 2026-06-13 07:07:50
● 2026-08-09 10:04:00
● 2026-06-13 07:07:50
● 2026-08-09 10:04:00
●NSlaunch2.spaceship.net2026-06-13 → 2026-08-09 · 3 obs
○ 2026-02-15 19:38:50
● 2026-06-13 07:07:50
● 2026-08-09 10:04:00
● 2026-06-13 07:07:50
● 2026-08-09 10:04:00
○NSns1.sedoparking.com2026-02-14 → 2026-02-15 · 5 obs
○ 2018-09-22 17:26:36
● 2026-02-14 20:41:10
● 2026-02-15 19:38:50
○ 2026-06-13 07:07:50
○ 2026-08-09 10:04:00
● 2026-02-14 20:41:10
● 2026-02-15 19:38:50
○ 2026-06-13 07:07:50
○ 2026-08-09 10:04:00
○NSns2.sedoparking.com2026-02-14 → 2026-02-15 · 5 obs
○ 2018-09-22 17:26:36
● 2026-02-14 20:41:10
● 2026-02-15 19:38:50
○ 2026-06-13 07:07:50
○ 2026-08-09 10:04:00
● 2026-02-14 20:41:10
● 2026-02-15 19:38:50
○ 2026-06-13 07:07:50
○ 2026-08-09 10:04:00
○NSredbusprimarydns.pacifictelegraph.com2017-02-02 → 2018-09-22 · 4 obs
● 2017-02-02 14:12:48
● 2018-09-22 17:26:36
○ 2026-02-14 20:41:10
○ 2026-08-09 10:04:00
● 2018-09-22 17:26:36
○ 2026-02-14 20:41:10
○ 2026-08-09 10:04:00
○NSredbussecondarydns.pacifictelegraph.com2017-02-02 → 2018-09-22 · 4 obs
● 2017-02-02 14:12:48
● 2018-09-22 17:26:36
○ 2026-02-14 20:41:10
○ 2026-08-09 10:04:00
● 2018-09-22 17:26:36
○ 2026-02-14 20:41:10
○ 2026-08-09 10:04:00
○MXlocalhost2026-02-14 → 2026-02-15 · 4 obs
● 2026-02-14 20:41:10
● 2026-02-15 19:38:50
○ 2026-06-13 07:07:50
○ 2026-08-09 10:04:00
● 2026-02-15 19:38:50
○ 2026-06-13 07:07:50
○ 2026-08-09 10:04:00
○A195.149.84.1002017-02-02 → 2018-09-22 · 4 obs
● 2017-02-02 14:12:48
● 2018-09-22 17:26:36
○ 2026-02-14 20:41:10
○ 2026-08-09 10:04:00
● 2018-09-22 17:26:36
○ 2026-02-14 20:41:10
○ 2026-08-09 10:04:00
○A195.149.84.1012017-02-02 → 2018-09-22 · 4 obs
● 2017-02-02 14:12:48
● 2018-09-22 17:26:36
○ 2026-02-14 20:41:10
○ 2026-08-09 10:04:00
● 2018-09-22 17:26:36
○ 2026-02-14 20:41:10
○ 2026-08-09 10:04:00
○A2001:67c:38c::642017-02-02 → 2018-09-22 · 4 obs
● 2017-02-02 14:12:48
● 2018-09-22 17:26:36
○ 2026-02-14 20:41:10
○ 2026-08-09 10:04:00
● 2018-09-22 17:26:36
○ 2026-02-14 20:41:10
○ 2026-08-09 10:04:00
○A2001:67c:38c::652017-02-02 → 2018-09-22 · 4 obs
● 2017-02-02 14:12:48
● 2018-09-22 17:26:36
○ 2026-02-14 20:41:10
○ 2026-08-09 10:04:00
● 2018-09-22 17:26:36
○ 2026-02-14 20:41:10
○ 2026-08-09 10:04:00
○A44.232.173.2492026-06-13 → 2026-06-13 · 3 obs
○ 2026-02-15 19:38:50
● 2026-06-13 07:07:50
○ 2026-08-09 10:04:00
● 2026-06-13 07:07:50
○ 2026-08-09 10:04:00
○A52.40.42.1132026-06-13 → 2026-06-13 · 3 obs
○ 2026-02-15 19:38:50
● 2026-06-13 07:07:50
○ 2026-08-09 10:04:00
● 2026-06-13 07:07:50
○ 2026-08-09 10:04:00
○A64.190.63.2222026-02-14 → 2026-02-15 · 5 obs
○ 2018-09-22 17:26:36
● 2026-02-14 20:41:10
● 2026-02-15 19:38:50
○ 2026-06-13 07:07:50
○ 2026-08-09 10:04:00
● 2026-02-14 20:41:10
● 2026-02-15 19:38:50
○ 2026-06-13 07:07:50
○ 2026-08-09 10:04:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, l.gtld-servers.net, d.gtld-servers.net, f.gtld-servers.net... | - |
| pacifictelegraph.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 pacifictelegraph.com
⏱️ Timing
Total: 1064ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 2 | 9e3321bd9bb793ae70971720020ba42b9b731ed6, e567a8f9fa887e43facb77ee53ab0e9074333b12 |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
Name Servers
pacifictelegraph.com is served by two delegated name servers, launch1.spaceship.net and launch2.spaceship.net.
pacifictelegraph.com uses the same name servers as several other domains — among them crunchnetworks.com, the-dog-house-slot.casino, muststash.co.uk and two more.
pacifictelegraph.com partially shares its name servers with domains like bclp.ca and delalex.com.
Each of the two host names carries two IP addresses: launch1.spaceship.net points to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26, and launch2.spaceship.net points to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.