`google-ticket.com`

DNSSEC	⚠️ Not signed
A	165.22.27.118^{🇩🇪 DIGITALOCEAN165.22.16.0/20 DigitalOcean}
NS	`ns1.fozzy.com` ⭐
		A	2607:fbe0:1:49::a^{🇺🇸 WZCOM-US2607:fbe0::/32 WZ US}
			PTR	`ns1.fozzy.com`
		A	206.54.190.9^{🇺🇸 WZCOM-US206.54.190.0/24 DAL-WZ}
			PTR	`ns1.fozzy.com`
NS	`ns2.fozzy.com`
		A	2a00:1178:1:66:6::2^{🇳🇱 WEBAZILLA2a00:1178::/32}
			PTR	`ns2.fozzy.com`
		A	88.85.81.2^{🇳🇱 WEBAZILLA88.85.81.0/24 WZ AMS specific route}
MX	`google-ticket.com` ⭐
		A	165.22.27.118^{🇩🇪 DIGITALOCEAN165.22.16.0/20 DigitalOcean}
TXT	`v=spf1 +a +mx +ip4:78.140.140.218 ~all`
SOA	`ns1.fozzy.com`root-cpanel@fozzy.com 2025-11-14 #2

`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=1771291435

⚠️ On DNS blocklist: tif

MX for

google-ticket.com

Same first word

google-ticket.com

DNS History

4 records (4 active, 0 former)

●NSns1.fozzy.com2026-03-15 → 2026-03-22 · 2 obs

● 2026-03-15 06:00:56
● 2026-03-22 23:44:46

●NSns2.fozzy.com2026-03-15 → 2026-03-22 · 2 obs

● 2026-03-15 06:00:56
● 2026-03-22 23:44:46

●MXgoogle-ticket.com2026-03-15 → 2026-03-22 · 2 obs

● 2026-03-15 06:00:56
● 2026-03-22 23:44:46

●A165.22.27.1182026-03-15 → 2026-03-22 · 2 obs

● 2026-03-15 06:00:56
● 2026-03-22 23:44:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
google-ticket.com	ns1.fozzy.com, ns2.fozzy.com	4 records

✅ Authoritative Response

Server:88.85.81.2

NS records: ns1.fozzy.com, ns2.fozzy.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for google-ticket.com (unsigned zone)

⏱️ Timing

Total: 367ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`165.22.27.118`
NS	2	`ns1.fozzy.com, ns2.fozzy.com`
MX	1	`google-ticket.com (pri: 0)`
TXT	1	`v=spf1 +a +mx +ip4:78.140.140.218 ~all`
SOA	1	`ns1.fozzy.com root-cpanel.fozzy.com`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.fozzy.com, ns1.fozzy.com, ns2.fozzy.com...)

Analysis

Mail Server Role

google-ticket.com serves as the mail server for google-ticket.com.

IP Addresses

google-ticket.com points to IP number: 165.22.27.118.

Other host names, for instance dogbreederapp.com share IP numbers with google-ticket.com.

Name Servers

google-ticket.com is delegated to two name servers: ns1.fozzy.com and ns2.fozzy.com.

google-ticket.com shares the same name server setup as metroway.ru, hot(0x696e63657374).club, roomribble.click, kromlyn.com and fintaca.com.

google-ticket.com at least partially shares name servers with other domains, for instance producm.ru, rjj.ru, d.fozzy.ru, live-gta.ru and parazit-off.ru.

these name servers are commonly used with ns1.fozzy.ru, ns2.fozzy.ru, ns2.8toinfinity.net and ns1.8toinfinity.net.

Host names with two IP numbers: ns1.fozzy.com points to: 2607:fbe0:1:49::a and 206.54.190.9; ns2.fozzy.com points to: 2a00:1178:1:66:6::2 and 88.85.81.2.

Mail Servers

google-ticket.com is handled by a single mail server, google-ticket.com.

google-ticket.com points to a single IP: 165.22.27.118.

google-ticket.com - robtex.com