hack.events - dns.ninja

hack.events

events

DNSSECπŸ”’ Signed (DS record present)
NSv0n0.nic.events ⭐
NSv0n1.nic.events
NSv0n2.nic.events
NSv0n3.nic.events
NSv2n0.nic.events
NSv2n1.nic.events
SOAv0n0.nic.eventshostmaster@donuts.email serial=1781790426

Same first word

Similar names

DNS History

10 records (4 active, 6 former)

2017201820192020202120222023202420252026NSns-cloud-b1.googledomains.comns-cloud-b2.googledomains.comns-cloud-b3.googledomains.comns-cloud-b4.googledomains.comns.udag.dens.udag.netns.udag.orgMXmx00.udag.demx01.udag.deA128.199.50.130
●NSns-cloud-b1.googledomains.com2026-02-15 β†’ 2026-06-18 Β· 3 obs
β—‹ 2017-11-10 13:05:16
● 2026-02-15 19:48:20
● 2026-06-18 14:18:38
●NSns-cloud-b2.googledomains.com2026-02-15 β†’ 2026-06-18 Β· 3 obs
β—‹ 2017-11-10 13:05:16
● 2026-02-15 19:48:20
● 2026-06-18 14:18:38
●NSns-cloud-b3.googledomains.com2026-02-15 β†’ 2026-06-18 Β· 3 obs
β—‹ 2017-11-10 13:05:16
● 2026-02-15 19:48:20
● 2026-06-18 14:18:38
●NSns-cloud-b4.googledomains.com2026-02-15 β†’ 2026-06-18 Β· 3 obs
β—‹ 2017-11-10 13:05:16
● 2026-02-15 19:48:20
● 2026-06-18 14:18:38
β—‹NSns.udag.de2016-12-10 β†’ 2017-11-10 Β· 4 obs
● 2016-12-10 21:18:52
● 2017-11-10 13:05:16
β—‹ 2026-02-15 19:48:20
β—‹ 2026-06-18 14:18:38
β—‹NSns.udag.net2016-12-10 β†’ 2017-11-10 Β· 4 obs
● 2016-12-10 21:18:52
● 2017-11-10 13:05:16
β—‹ 2026-02-15 19:48:20
β—‹ 2026-06-18 14:18:38
β—‹NSns.udag.org2016-12-10 β†’ 2017-11-10 Β· 4 obs
● 2016-12-10 21:18:52
● 2017-11-10 13:05:16
β—‹ 2026-02-15 19:48:20
β—‹ 2026-06-18 14:18:38
β—‹MXmx00.udag.de2016-12-10 β†’ 2026-02-15 Β· 4 obs
● 2016-12-10 21:18:52
● 2026-02-15 19:48:20
β—‹ 2026-02-20 13:04:08
β—‹ 2026-06-18 14:18:38
β—‹MXmx01.udag.de2016-12-10 β†’ 2026-02-15 Β· 4 obs
● 2016-12-10 21:18:52
● 2026-02-15 19:48:20
β—‹ 2026-02-20 13:04:08
β—‹ 2026-06-18 14:18:38
β—‹A128.199.50.1302016-12-10 β†’ 2026-02-15 Β· 4 obs
● 2016-12-10 21:18:52
● 2026-02-15 19:48:20
β—‹ 2026-02-20 13:04:08
β—‹ 2026-06-18 14:18:38

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
eventsv0n0.nic.events, v0n2.nic.events, v2n0.nic.events, v0n1.nic.events...12 records
hack.eventsns-cloud-b1.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b4.googledomains.com-

βœ… Authoritative Response

Server:216.239.38.107

NS records: ns-cloud-b1.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b4.googledomains.com

πŸ”’ DNSSEC Status

πŸ” Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 645ms | Queries: -

πŸ“„ Records

TypeCountSample Data
NS4ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com...
SOA1ns-cloud-b1.googledomains.com cloud-dns-

πŸ“Œ Glue Records Collected

Total: 12

In-bailiwick: 12 (v0n0.nic.events, v0n0.nic.events, v0n2.nic.events...)

Analysis

Name Servers

The NS records for hack.events point to four name servers: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com.

There is at least partial name server overlap between hack.events and other domains β€” ilma.us, kwito.com, todozen.com and two more among them.

All four hostnames β€” ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com β€” resolve to two IP numbers apiece: ns-cloud-b1.googledomains.com to 216.239.32.107 and 2001:4860:4802:32::6b; ns-cloud-b2.googledomains.com to 216.239.34.107 and 2001:4860:4802:34::6b; ns-cloud-b3.googledomains.com to 216.239.36.107 and 2001:4860:4802:36::6b; ns-cloud-b4.googledomains.com to 216.239.38.107 and 2001:4860:4802:38::6b.