cho.to - robtex.com

cho.to

DNSSEC⚠️ Not signed
A34.216.117.25πŸ‡ΊπŸ‡Έ Amazon34.208.0.0/12 EC2 PDX prefix
PTRec2-34-216-117-25.us-west-2.compute.amazonaws.com
A54.149.79.189πŸ‡ΊπŸ‡Έ Amazon54.148.0.0/15 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
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
SOAlaunch1.spaceship.netsupport@spaceship.com serial=1766937443

to

DNSSEC⚠️ Not signed
NSns01.trs-dns.com ⭐
NSns.trs-dns.com
NSns01.trs-dns.net
NSns10.trs-dns.info
NSns10.trs-dns.org
SOAns.trs-dns.comtrs-ops@tucows.com serial=1775976018
WOT: SAFE (64/100)

Same first word

Similar names

DNS History

8 records (4 active, 4 former)

20162017201820192020202120222023202420252026NSlaunch1.spaceship.netlaunch2.spaceship.netdns1.yandex.netdns2.yandex.netMXmx.yandex.netA34.216.117.2554.149.79.189194.28.172.243
β—‹NSdns1.yandex.net2015-10-26 β†’ 2016-12-28 Β· 4 obs
● 2015-10-26 13:50:36
● 2016-12-28 03:45:58
β—‹ 2026-03-26 12:15:42
β—‹ 2026-04-12 06:52:12
β—‹NSdns2.yandex.net2015-10-26 β†’ 2016-12-28 Β· 4 obs
● 2015-10-26 13:50:36
● 2016-12-28 03:45:58
β—‹ 2026-03-26 12:15:42
β—‹ 2026-04-12 06:52:12
●NSlaunch1.spaceship.net2026-03-26 β†’ 2026-04-12 Β· 3 obs
β—‹ 2016-12-28 03:45:58
● 2026-03-26 12:15:42
● 2026-04-12 06:52:12
●NSlaunch2.spaceship.net2026-03-26 β†’ 2026-04-12 Β· 3 obs
β—‹ 2016-12-28 03:45:58
● 2026-03-26 12:15:42
● 2026-04-12 06:52:12
β—‹MXmx.yandex.net2015-10-26 β†’ 2016-12-28 Β· 4 obs
● 2015-10-26 13:50:36
● 2016-12-28 03:45:58
β—‹ 2026-03-26 12:15:42
β—‹ 2026-04-12 06:52:12
β—‹A194.28.172.2432015-10-26 β†’ 2016-12-28 Β· 4 obs
● 2015-10-26 13:50:36
● 2016-12-28 03:45:58
β—‹ 2026-03-26 12:15:42
β—‹ 2026-04-12 06:52:12
●A34.216.117.252026-03-26 β†’ 2026-04-12 Β· 3 obs
β—‹ 2016-12-28 03:45:58
● 2026-03-26 12:15:42
● 2026-04-12 06:52:12
●A54.149.79.1892026-03-26 β†’ 2026-04-12 Β· 3 obs
β—‹ 2016-12-28 03:45:58
● 2026-03-26 12:15:42
● 2026-04-12 06:52:12

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
tons01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info8 records
cho.tolaunch2.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 to (unsigned zone)

⏱️ Timing

Total: 458ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A254.149.79.189, 34.216.117.25
NS2launch1.spaceship.net, launch2.spaceship.net
SOA1launch1.spaceship.net support.spaceship.

πŸ“Œ Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org...)

Analysis

IP Addresses

cho.to points to two IPs: 34.216.117.25 and 54.149.79.189.

Other host names including inkest.org, idaccounts.com, birdersview.com, cloudemail.net and donkeynote.com share IP numbers with cho.to.

Name Servers

cho.to's delegation uses two name servers, launch1.spaceship.net and launch2.spaceship.net.

cho.to shares the same name server setup as other domains, for example peacemonth.org, oyunda.net, jensellsdestin.com, near-me.in and venjay.com.

cho.to at least partially shares name servers with other domains; for instance appstreem.com.

Host names with two IPs:

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