cryptocmo.com - robtex.com
cryptocmo.com
| DNSSEC | β οΈ Not signed | ||||||
| A | 31.77.192.66π¬π§ BT-UK-AS31.64.0.0/12 | ||||||
| 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 | b9b084e5-c235-4183-b4db-2fc3607733e7 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1781006613 | ||||||
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=1787471446 | ||||||
Same first word
cryptocmo.com |
Similar names
Previous names
Next names
DNS History
12 records (3 active, 9 former)
βNSlaunch1.spaceship.net2026-08-18 β 2026-08-23 Β· 3 obs
β 2026-08-18 14:34:30
β 2026-08-23 08:14:52
βNSlaunch2.spaceship.net2026-08-18 β 2026-08-23 Β· 3 obs
β 2026-08-18 14:34:30
β 2026-08-23 08:14:52
βNSns13.domaincontrol.com2018-01-11 β 2018-01-11 Β· 3 obs
β 2026-08-18 14:34:30
β 2026-08-23 08:14:52
βNSns14.domaincontrol.com2018-01-11 β 2018-01-11 Β· 3 obs
β 2026-08-18 14:34:30
β 2026-08-23 08:14:52
βA184.168.221.332018-01-11 β 2018-01-11 Β· 3 obs
β 2026-08-18 14:34:30
β 2026-08-23 08:14:52
βA184.168.221.482018-01-11 β 2018-01-11 Β· 3 obs
β 2026-08-18 14:34:30
β 2026-08-23 08:14:52
βA184.168.221.562018-01-11 β 2018-01-11 Β· 3 obs
β 2026-08-18 14:34:30
β 2026-08-23 08:14:52
βA31.77.192.662026-08-18 β 2026-08-23 Β· 3 obs
β 2026-08-18 14:34:30
β 2026-08-23 08:14:52
βA50.63.202.322018-01-11 β 2018-01-11 Β· 3 obs
β 2026-08-18 14:34:30
β 2026-08-23 08:14:52
βA50.63.202.552018-01-11 β 2018-01-11 Β· 3 obs
β 2026-08-18 14:34:30
β 2026-08-23 08:14:52
βA50.63.202.572018-01-11 β 2018-01-11 Β· 3 obs
β 2026-08-18 14:34:30
β 2026-08-23 08:14:52
βA50.63.202.592018-01-11 β 2018-01-11 Β· 3 obs
β 2026-08-18 14:34:30
β 2026-08-23 08:14:52
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| cryptocmo.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)
DS for cryptocmo.com does not match any DNSKEY
β±οΈ Timing
Total: 1327ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 31.77.192.66 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 1 | b9b084e5-c235-4183-b4db-2fc3607733e7 |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
cryptocmo.com directs to one IP number, which is 31.77.192.66.
Among the host names that share IP numbers with cryptocmo.com are oofff.com, cryptocoinnet.com, onluxe.com and two others.
Name Servers
The NS records for cryptocmo.com delegate to launch1.spaceship.net and launch2.spaceship.net.
cryptocmo.com has the same name server delegation as a number of other domains, such as itmat.site, imperatorov-sokrovisha-final.sbs, salinecountychamber.org and two more.
cryptocmo.com at least partially shares name servers with other domains, including westartist.com, zaccour.com, dogtrainingobedience.com and roodns.com.
These name servers are frequently seen alongside the name servers verification-mdzaaqbc9wh5xb8j4cudbd.ns101.verify.hn.
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.