🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`blockinghamfc.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::6815:3fa^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:8363^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.3.250^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.131.99^{🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`karsyn.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:26c2^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`karsyn.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2c2^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`karsyn.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22c2^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`karsyn.ns.cloudflare.com`
		A	108.162.194.194^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`karsyn.ns.cloudflare.com`
		A	162.159.38.194^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`karsyn.ns.cloudflare.com`
		A	172.64.34.194^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`karsyn.ns.cloudflare.com`
NS	`titan.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c5d^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`titan.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c35d^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`titan.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:235d^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`titan.ns.cloudflare.com`
		A	108.162.195.93^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`titan.ns.cloudflare.com`
		A	162.159.44.93^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`titan.ns.cloudflare.com`
		A	172.64.35.93^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`titan.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.3.250, 172.67.131.99
		IPv6 hints	2606:4700:3031::6815:3fa, 2606:4700:3037::ac43:8363
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=226, name=cloudflare-ech.com
SOA	`karsyn.ns.cloudflare.com`dns@cloudflare.com serial=2419334530

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

Same first word

blockinghamfc.com

Similar names

mfgblockchain.com

Previous names

Next names

DNS History

6 records (6 active, 0 former)

●NSkarsyn.ns.cloudflare.com2026-09-12 → 2026-11-08 · 2 obs

● 2026-09-12 01:57:38
● 2026-11-08 21:23:06

●NStitan.ns.cloudflare.com2026-09-12 → 2026-11-08 · 2 obs

● 2026-09-12 01:57:38
● 2026-11-08 21:23:06

●A104.21.3.2502026-09-12 → 2026-11-08 · 2 obs

● 2026-09-12 01:57:38
● 2026-11-08 21:23:06

●A172.67.131.992026-09-12 → 2026-11-08 · 2 obs

● 2026-09-12 01:57:38
● 2026-11-08 21:23:06

●A2606:4700:3031::6815:3fa2026-09-12 → 2026-11-08 · 2 obs

● 2026-09-12 01:57:38
● 2026-11-08 21:23:06

●A2606:4700:3037::ac43:83632026-09-12 → 2026-11-08 · 2 obs

● 2026-09-12 01:57:38
● 2026-11-08 21:23:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, g.gtld-servers.net...	-
blockinghamfc.com	karsyn.ns.cloudflare.com, titan.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:172.64.35.93

NS records: karsyn.ns.cloudflare.com, titan.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for blockinghamfc.com (unsigned zone)

⏱️ Timing

Total: 549ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.131.99, 104.21.3.250`
AAAA	2	`2606:4700:3037::ac43:8363, 2606:4700:3031::6815:3fa`
NS	2	`karsyn.ns.cloudflare.com, titan.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`karsyn.ns.cloudflare.com dns.cloudflare.`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

blockinghamfc.com directs to four IP numbers, which are 104.21.3.250, 172.67.131.99, 2606:4700:3031::6815:3fa and 2606:4700:3037::ac43:8363.

getcontainercosts.com, quest-npc.sumy.ua, rememefun.com and two other host names share IP numbers with blockinghamfc.com.

Name Servers

blockinghamfc.com is delegated to two name servers: karsyn.ns.cloudflare.com and titan.ns.cloudflare.com.

blockinghamfc.com uses the same name servers as several other domains — among them cloudmasterpro.com, sgcuan-5.pages.dev, browsenews.pages.dev and two more.

At least some of blockinghamfc.com's name servers are shared with other domains, for example magic-planet.net, hub-os.workers.dev, mega303meledak.com and two more.

These name servers are often deployed together with the name servers treasure.ns.cloudflare.com, chase.ns.cloudflare.com, ligia.ns.cloudflare.com and sean.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

karsyn.ns.cloudflare.com resolves to 108.162.194.194, 162.159.38.194, 172.64.34.194 and 3 other IP addresses.

titan.ns.cloudflare.com resolves to 108.162.195.93, 162.159.44.93, 172.64.35.93 and 3 other IP addresses.

blockinghamfc.com - robtex.com