🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`ticket-surf.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::6815:56bd^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3035::ac43:8819^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.86.189^{Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.136.25^{🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`jo.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3aac^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jo.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0ac^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`jo.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20ac^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`jo.ns.cloudflare.com`
		A	108.162.192.172^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jo.ns.cloudflare.com`
		A	172.64.32.172^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jo.ns.cloudflare.com`
		A	173.245.58.172^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jo.ns.cloudflare.com`
NS	`mcgrory.ns.cloudflare.com`
		A	2606:4700:58::a29f:2caa^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`mcgrory.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c3aa^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`mcgrory.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:23aa^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`mcgrory.ns.cloudflare.com`
		A	108.162.195.170^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`mcgrory.ns.cloudflare.com`
		A	162.159.44.170^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`mcgrory.ns.cloudflare.com`
		A	172.64.35.170^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`mcgrory.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.86.189, 172.67.136.25
		IPv6 hints	2606:4700:3030::6815:56bd, 2606:4700:3035::ac43:8819
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=66, name=cloudflare-ech.com
SOA	`jo.ns.cloudflare.com`dns@cloudflare.com serial=2412437638

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

WOT: SAFE (63/100)

Same first word

ticket-surf.com

DNS History

21 records (9 active, 12 former)

○NSa.dns.gandi.net2017-12-30 → 2017-12-30 · 4 obs

○ 2017-01-05 09:52:52
● 2017-12-30 02:29:34
○ 2026-05-09 10:11:12
○ 2026-08-17 14:43:34

○NSb.dns.gandi.net2017-12-30 → 2017-12-30 · 4 obs

○ 2017-01-05 09:52:52
● 2017-12-30 02:29:34
○ 2026-05-09 10:11:12
○ 2026-08-17 14:43:34

○NSc.dns.gandi.net2017-12-30 → 2017-12-30 · 4 obs

○ 2017-01-05 09:52:52
● 2017-12-30 02:29:34
○ 2026-05-09 10:11:12
○ 2026-08-17 14:43:34

●NSjo.ns.cloudflare.com2026-06-25 → 2026-08-17 · 3 obs

○ 2026-05-09 10:11:12
● 2026-06-25 17:24:40
● 2026-08-17 14:43:34

●NSmcgrory.ns.cloudflare.com2026-06-25 → 2026-08-17 · 3 obs

○ 2026-05-09 10:11:12
● 2026-06-25 17:24:40
● 2026-08-17 14:43:34

○NSns1.vinc.fr2015-06-06 → 2017-01-05 · 4 obs

● 2015-06-06 06:13:24
● 2017-01-05 09:52:52
○ 2017-12-30 02:29:34
○ 2026-08-17 14:43:34

○NSns2.vinc.fr2015-06-06 → 2017-01-05 · 4 obs

● 2015-06-06 06:13:24
● 2017-01-05 09:52:52
○ 2017-12-30 02:29:34
○ 2026-08-17 14:43:34

○MXalt1.aspmx.l.google.com2015-06-06 → 2017-12-30 · 4 obs

● 2015-06-06 06:13:24
● 2017-12-30 02:29:34
○ 2026-05-09 10:11:12
○ 2026-08-17 14:43:34

○MXalt2.aspmx.l.google.com2015-06-06 → 2017-12-30 · 4 obs

● 2015-06-06 06:13:24
● 2017-12-30 02:29:34
○ 2026-05-09 10:11:12
○ 2026-08-17 14:43:34

○MXaspmx.l.google.com2015-06-06 → 2017-12-30 · 4 obs

● 2015-06-06 06:13:24
● 2017-12-30 02:29:34
○ 2026-05-09 10:11:12
○ 2026-08-17 14:43:34

○MXaspmx2.googlemail.com2015-06-06 → 2017-12-30 · 4 obs

● 2015-06-06 06:13:24
● 2017-12-30 02:29:34
○ 2026-05-09 10:11:12
○ 2026-08-17 14:43:34

○MXaspmx3.googlemail.com2015-06-06 → 2017-12-30 · 4 obs

● 2015-06-06 06:13:24
● 2017-12-30 02:29:34
○ 2026-05-09 10:11:12
○ 2026-08-17 14:43:34

●MXroute1.mx.cloudflare.net2026-06-25 → 2026-08-17 · 3 obs

○ 2026-05-09 10:11:12
● 2026-06-25 17:24:40
● 2026-08-17 14:43:34

●MXroute2.mx.cloudflare.net2026-06-25 → 2026-08-17 · 3 obs

○ 2026-05-09 10:11:12
● 2026-06-25 17:24:40
● 2026-08-17 14:43:34

●MXroute3.mx.cloudflare.net2026-06-25 → 2026-08-17 · 3 obs

○ 2026-05-09 10:11:12
● 2026-06-25 17:24:40
● 2026-08-17 14:43:34

●A104.21.86.1892026-06-25 → 2026-08-17 · 3 obs

○ 2026-05-09 10:11:12
● 2026-06-25 17:24:40
● 2026-08-17 14:43:34

●A172.67.136.252026-06-25 → 2026-08-17 · 3 obs

○ 2026-05-09 10:11:12
● 2026-06-25 17:24:40
● 2026-08-17 14:43:34

○A213.182.44.1312017-12-30 → 2017-12-30 · 4 obs

○ 2017-01-05 09:52:52
● 2017-12-30 02:29:34
○ 2026-05-09 10:11:12
○ 2026-08-17 14:43:34

●A2606:4700:3030::6815:56bd2026-06-25 → 2026-08-17 · 3 obs

○ 2026-05-09 10:11:12
● 2026-06-25 17:24:40
● 2026-08-17 14:43:34

●A2606:4700:3035::ac43:88192026-06-25 → 2026-08-17 · 3 obs

○ 2026-05-09 10:11:12
● 2026-06-25 17:24:40
● 2026-08-17 14:43:34

○A89.30.106.2352015-06-06 → 2017-01-05 · 4 obs

● 2015-06-06 06:13:24
● 2017-01-05 09:52:52
○ 2017-12-30 02:29:34
○ 2026-08-17 14:43:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
ticket-surf.com	jo.ns.cloudflare.com, mcgrory.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.192.172

NS records: jo.ns.cloudflare.com, mcgrory.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 279ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.86.189, 172.67.136.25`
AAAA	2	`2606:4700:3030::6815:56bd, 2606:4700:3035::ac43:8819`
NS	2	`jo.ns.cloudflare.com, mcgrory.ns.cloudflare.com`
MX	3	`route2.mx.cloudflare.net (pri: 38), route1.mx.cloudflare.net (pri: 54)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`jo.ns.cloudflare.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

ticket-surf.com points to the four IP addresses 104.21.86.189, 172.67.136.25, 2606:4700:3030::6815:56bd and 2606:4700:3035::ac43:8819.

tirreno.com.br, spiritualwest.com, xyzsports-1f2df0dd8c.xyz plus two other host names have IP numbers in common with ticket-surf.com.

Name Servers

ticket-surf.com is served by two delegated name servers, jo.ns.cloudflare.com and mcgrory.ns.cloudflare.com.

The name server configuration of ticket-surf.com is shared with other domains, for instance veja-store.com.br, ipublishing.co.in, stats-reports.com and two others.

There is at least partial name server overlap between ticket-surf.com and other domains — kached.go.th, msfxs.net, haxu9.com and two more among them.

Hosts with 6 IP addresses each:

jo.ns.cloudflare.com carries IP addresses 108.162.192.172, 172.64.32.172 and 173.245.58.172, with 3 other addresses beyond those.

mcgrory.ns.cloudflare.com carries IP addresses 108.162.195.170, 162.159.44.170 and 172.64.35.170, with 3 other addresses beyond those.

Mail Servers

Incoming mail for ticket-surf.com is delivered via three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

At least some of the mail servers used by ticket-surf.com are shared with other domains: dabvastur.site, alfawzan.org, fleebaybaby.cyou and two others among them.

Hosts with 6 IP addresses each:

route1.mx.cloudflare.net carries IP addresses 162.159.205.11, 162.159.205.12 and 162.159.205.13, with 3 other addresses beyond those.

route2.mx.cloudflare.net carries IP addresses 162.159.205.17, 162.159.205.18 and 162.159.205.19, with 3 other addresses beyond those.

route3.mx.cloudflare.net carries IP addresses 162.159.205.23, 162.159.205.24 and 162.159.205.25, with 3 other addresses beyond those.

ticket-surf.com - robtex.com

ticket-surf.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

`ticket-surf.com`

`com`