crypto-ticket.com - robtex.com

crypto-ticket.com

com

Same first word

DNS History

12 records (4 active, 8 former)

201820192020202120222023202420252026NSns-cloud-c1.googledomains.comns-cloud-c2.googledomains.comns-cloud-c3.googledomains.comns-cloud-c4.googledomains.comns1034.ui-dns.comns1063.ui-dns.orgns1102.ui-dns.bizns1110.ui-dns.deMXmx00.kundenserver.demx01.kundenserver.deA2001:8d8:100f:f000::2f0217.160.0.133
●NSns-cloud-c1.googledomains.com2026-03-24 β†’ 2026-03-24 Β· 2 obs
β—‹ 2017-11-10 04:47:36
● 2026-03-24 11:42:14
●NSns-cloud-c2.googledomains.com2026-03-24 β†’ 2026-03-24 Β· 2 obs
β—‹ 2017-11-10 04:47:36
● 2026-03-24 11:42:14
●NSns-cloud-c3.googledomains.com2026-03-24 β†’ 2026-03-24 Β· 2 obs
β—‹ 2017-11-10 04:47:36
● 2026-03-24 11:42:14
●NSns-cloud-c4.googledomains.com2026-03-24 β†’ 2026-03-24 Β· 2 obs
β—‹ 2017-11-10 04:47:36
● 2026-03-24 11:42:14
β—‹NSns1034.ui-dns.com2017-11-10 β†’ 2017-11-10 Β· 2 obs
● 2017-11-10 04:47:36
β—‹ 2026-03-24 11:42:14
β—‹NSns1063.ui-dns.org2017-11-10 β†’ 2017-11-10 Β· 2 obs
● 2017-11-10 04:47:36
β—‹ 2026-03-24 11:42:14
β—‹NSns1102.ui-dns.biz2017-11-10 β†’ 2017-11-10 Β· 2 obs
● 2017-11-10 04:47:36
β—‹ 2026-03-24 11:42:14
β—‹NSns1110.ui-dns.de2017-11-10 β†’ 2017-11-10 Β· 2 obs
● 2017-11-10 04:47:36
β—‹ 2026-03-24 11:42:14
β—‹MXmx00.kundenserver.de2017-11-10 β†’ 2017-11-10 Β· 2 obs
● 2017-11-10 04:47:36
β—‹ 2026-03-24 11:42:14
β—‹MXmx01.kundenserver.de2017-11-10 β†’ 2017-11-10 Β· 2 obs
● 2017-11-10 04:47:36
β—‹ 2026-03-24 11:42:14
β—‹A2001:8d8:100f:f000::2f02017-11-10 β†’ 2017-11-10 Β· 2 obs
● 2017-11-10 04:47:36
β—‹ 2026-03-24 11:42:14
β—‹A217.160.0.1332017-11-10 β†’ 2017-11-10 Β· 2 obs
● 2017-11-10 04:47:36
β—‹ 2026-03-24 11:42:14

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
crypto-ticket.comns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com8 records

βœ… Authoritative Response

Server:216.239.38.108

NS records: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com

πŸ”’ DNSSEC Status

πŸ” Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 275ms | Queries: -

πŸ“„ Records

TypeCountSample Data
NS4ns-cloud-c4.googledomains.com, ns-cloud-c1.googledomains.com...
SOA1ns-cloud-c1.googledomains.com cloud-dns-

πŸ“Œ Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-c1.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com...)

Analysis

Name Servers

crypto-ticket.com is delegated to four name servers: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com.

crypto-ticket.com at least partially shares name servers with other domains, for instance londonsophia.com, rockies.cn, drdlawoffices.com, jimmylewismows.com and tennisluv.com.

Host names with two IP numbers:

ns-cloud-c1.googledomains.com points to 2001:4860:4802:32::6c and 216.239.32.108; ns-cloud-c2.googledomains.com points to 2001:4860:4802:34::6c and 216.239.34.108; ns-cloud-c3.googledomains.com points to 2001:4860:4802:36::6c and 216.239.36.108; ns-cloud-c4.googledomains.com points to 2001:4860:4802:38::6c and 216.239.38.108.