`eventofy.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::6815:3153^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:a06e^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.49.83^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.160.110^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`coco.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a68^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`coco.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c068^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`coco.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2068^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`coco.ns.cloudflare.com`
		A	108.162.192.104^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`coco.ns.cloudflare.com`
		A	172.64.32.104^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`coco.ns.cloudflare.com`
		A	173.245.58.104^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`coco.ns.cloudflare.com`
NS	`west.ns.cloudflare.com`
		A	2606:4700:58::adf5:3bf7^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`west.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1f7^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`west.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21f7^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`west.ns.cloudflare.com`
		A	108.162.193.247^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`west.ns.cloudflare.com`
		A	172.64.33.247^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`west.ns.cloudflare.com`
		A	173.245.59.247^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`west.ns.cloudflare.com`
MX	`route2.mx.cloudflare.net` ⭐
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route1.mx.cloudflare.net`⁽⁶⁸⁾
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽⁷⁸⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.49.83, 172.67.160.110
		IPv6 hints	2606:4700:3031::6815:3153, 2606:4700:3037::ac43:a06e
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=65, name=cloudflare-ech.com
SOA	`coco.ns.cloudflare.com`dns@cloudflare.com serial=2410565397

`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.net`nstld@verisign-grs.com serial=1785839622

Same first word

eventofy.com

DNS History

24 records (9 active, 15 former)

●NScoco.ns.cloudflare.com2026-04-20 → 2026-08-04 · 3 obs

○ 2018-12-05 10:48:20
● 2026-04-20 08:07:08
● 2026-08-04 10:55:20

○NSdns11.parkpage.foundationapi.com2016-01-17 → 2016-01-17 · 4 obs

○ 2015-10-25 10:01:00
● 2016-01-17 02:41:58
○ 2016-04-30 22:28:36
○ 2026-08-04 10:55:20

○NSdns12.parkpage.foundationapi.com2016-01-17 → 2016-01-17 · 4 obs

○ 2015-10-25 10:01:00
● 2016-01-17 02:41:58
○ 2016-04-30 22:28:36
○ 2026-08-04 10:55:20

○NSns1.whois.com2015-05-31 → 2015-10-25 · 4 obs

● 2015-05-31 09:57:56
● 2015-10-25 10:01:00
○ 2016-01-17 02:41:58
○ 2026-08-04 10:55:20

○NSns2.dnsdun.com2018-12-05 → 2018-12-05 · 4 obs

○ 2016-04-30 22:28:36
● 2018-12-05 10:48:20
○ 2026-04-20 08:07:08
○ 2026-08-04 10:55:20

○NSns2.dnsdun.net2018-12-05 → 2018-12-05 · 4 obs

○ 2016-04-30 22:28:36
● 2018-12-05 10:48:20
○ 2026-04-20 08:07:08
○ 2026-08-04 10:55:20

○NSns2.whois.com2015-05-31 → 2015-10-25 · 4 obs

● 2015-05-31 09:57:56
● 2015-10-25 10:01:00
○ 2016-01-17 02:41:58
○ 2026-08-04 10:55:20

○NSns3.whois.com2015-05-31 → 2015-10-25 · 4 obs

● 2015-05-31 09:57:56
● 2015-10-25 10:01:00
○ 2016-01-17 02:41:58
○ 2026-08-04 10:55:20

○NSns4.whois.com2015-05-31 → 2015-10-25 · 4 obs

● 2015-05-31 09:57:56
● 2015-10-25 10:01:00
○ 2016-01-17 02:41:58
○ 2026-08-04 10:55:20

●NSwest.ns.cloudflare.com2026-04-20 → 2026-08-04 · 3 obs

○ 2018-12-05 10:48:20
● 2026-04-20 08:07:08
● 2026-08-04 10:55:20

○MX4511c1ba43da5648aa6e3fadd49a98.msv1.invalid2015-05-31 → 2015-10-25 · 4 obs

● 2015-05-31 09:57:56
● 2015-10-25 10:01:00
○ 2016-01-17 02:41:58
○ 2026-08-04 10:55:20

○MX4511c1ba43da5648aa6e3fadd49a98.pamx1.hotmail.com2015-05-31 → 2015-10-25 · 4 obs

● 2015-05-31 09:57:56
● 2015-10-25 10:01:00
○ 2016-01-17 02:41:58
○ 2026-08-04 10:55:20

●MXroute1.mx.cloudflare.net2026-04-20 → 2026-08-04 · 3 obs

○ 2016-01-17 02:41:58
● 2026-04-20 08:07:08
● 2026-08-04 10:55:20

●MXroute2.mx.cloudflare.net2026-04-20 → 2026-08-04 · 3 obs

○ 2016-01-17 02:41:58
● 2026-04-20 08:07:08
● 2026-08-04 10:55:20

●MXroute3.mx.cloudflare.net2026-04-20 → 2026-08-04 · 3 obs

○ 2016-01-17 02:41:58
● 2026-04-20 08:07:08
● 2026-08-04 10:55:20

○A104.149.15.522018-12-05 → 2018-12-05 · 4 obs

○ 2016-04-30 22:28:36
● 2018-12-05 10:48:20
○ 2026-04-20 08:07:08
○ 2026-08-04 10:55:20

●A104.21.49.832026-04-20 → 2026-08-04 · 3 obs

○ 2018-12-05 10:48:20
● 2026-04-20 08:07:08
● 2026-08-04 10:55:20

●A172.67.160.1102026-04-20 → 2026-08-04 · 3 obs

○ 2018-12-05 10:48:20
● 2026-04-20 08:07:08
● 2026-08-04 10:55:20

○A204.11.58.772015-05-31 → 2015-10-25 · 4 obs

● 2015-05-31 09:57:56
● 2015-10-25 10:01:00
○ 2016-01-17 02:41:58
○ 2026-08-04 10:55:20

○A209.99.40.2232016-01-17 → 2016-01-17 · 4 obs

○ 2015-10-25 10:01:00
● 2016-01-17 02:41:58
○ 2016-04-30 22:28:36
○ 2026-08-04 10:55:20

●A2606:4700:3031::6815:31532026-06-21 → 2026-08-04 · 3 obs

○ 2026-04-20 08:07:08
● 2026-06-21 23:11:26
● 2026-08-04 10:55:20

○A2606:4700:3032::6815:31532026-04-20 → 2026-04-20 · 4 obs

○ 2018-12-05 10:48:20
● 2026-04-20 08:07:08
○ 2026-06-21 23:11:26
○ 2026-08-04 10:55:20

○A2606:4700:3036::ac43:a06e2026-04-20 → 2026-04-20 · 4 obs

○ 2018-12-05 10:48:20
● 2026-04-20 08:07:08
○ 2026-06-21 23:11:26
○ 2026-08-04 10:55:20

●A2606:4700:3037::ac43:a06e2026-06-21 → 2026-08-04 · 3 obs

○ 2026-04-20 08:07:08
● 2026-06-21 23:11:26
● 2026-08-04 10:55:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, h.gtld-servers.net, j.gtld-servers.net, m.gtld-servers.net...	-
eventofy.com	coco.ns.cloudflare.com, west.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.192.104

NS records: coco.ns.cloudflare.com, west.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for eventofy.com (unsigned zone)

⏱️ Timing

Total: 127ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.160.110, 104.21.49.83`
AAAA	2	`2606:4700:3037::ac43:a06e, 2606:4700:3031::6815:3153`
NS	2	`coco.ns.cloudflare.com, west.ns.cloudflare.com`
MX	3	`route2.mx.cloudflare.net (pri: 10), route1.mx.cloudflare.net (pri: 68)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`coco.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (coco.ns.cloudflare.com, coco.ns.cloudflare.com, coco.ns.cloudflare.com...)

Analysis

IP Addresses

eventofy.com resolves to four IP addresses: 104.21.49.83, 172.67.160.110, 2606:4700:3031::6815:3153 and 2606:4700:3037::ac43:a06e.

Two other host names, along with sabeel.org.uk, lbdhomes.com.au and www.galiysana.vip, also share IP numbers with eventofy.com.

Name Servers

eventofy.com has two authoritative name servers — coco.ns.cloudflare.com and west.ns.cloudflare.com.

eventofy.com shares its NS records with other domains, for example sport-net.org, alexandremeloadvocacia.top, grassphere.com and two others.

eventofy.com has at least partial name server overlap with other domains, such as tonstudio.ru, zaspas.cz, 360e788ac3bd.com and two others.

It is common to see these name servers used together with name servers ernest.ns.cloudflare.com and art.ns.cloudflare.com.

DNS names with 6 IP addresses:

coco.ns.cloudflare.com points to 108.162.192.104, 172.64.32.104, 173.245.58.104 and 3 other IP addresses.

west.ns.cloudflare.com points to 108.162.193.247, 172.64.33.247, 173.245.59.247 and 3 other IP addresses.

Mail Servers

eventofy.com has three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

There is at least a partial MX overlap between eventofy.com and other domains, including tracelume.com, paunero.com, duongsinhannhien.com and two others.

DNS names with 6 IP addresses:

route1.mx.cloudflare.net points to 162.159.205.11, 162.159.205.12, 162.159.205.13 and 3 other IP addresses.

route2.mx.cloudflare.net points to 162.159.205.17, 162.159.205.18, 162.159.205.19 and 3 other IP addresses.

route3.mx.cloudflare.net points to 162.159.205.23, 162.159.205.24, 162.159.205.25 and 3 other IP addresses.

eventofy.com - robtex.com

eventofy.com

com

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`eventofy.com`

`com`