`chefclearance.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3032::6815:5986^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3033::ac43:9fcb^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.89.134^{Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.159.203^{🇺🇸 Cloudflare172.67.144.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`ashley.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a47^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ashley.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c047^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ashley.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2047^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ashley.ns.cloudflare.com`
		A	108.162.192.71^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ashley.ns.cloudflare.com`
		A	172.64.32.71^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ashley.ns.cloudflare.com`
		A	173.245.58.71^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ashley.ns.cloudflare.com`
NS	`walt.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b94^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`walt.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c194^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`walt.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2194^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`walt.ns.cloudflare.com`
		A	108.162.193.148^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`walt.ns.cloudflare.com`
		A	172.64.33.148^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`walt.ns.cloudflare.com`
		A	173.245.59.148^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`walt.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4	104.21.89.134, 172.67.159.203
		IPv6	2606:4700:3032::6815:5986, 2606:4700:3033::ac43:9fcb
SOA	`ashley.ns.cloudflare.com`dns@cloudflare.com serial=2397870771

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

⚠️ On DNS blocklist: tif

Same first word

chefclearance.com

DNS History

6 records (6 active, 0 former)

●NSashley.ns.cloudflare.com2026-03-19 → 2026-03-26 · 2 obs

● 2026-03-19 21:04:48
● 2026-03-26 21:34:44

●NSwalt.ns.cloudflare.com2026-03-19 → 2026-03-26 · 2 obs

● 2026-03-19 21:04:48
● 2026-03-26 21:34:44

●A104.21.89.1342026-03-19 → 2026-03-26 · 2 obs

● 2026-03-19 21:04:48
● 2026-03-26 21:34:44

●A172.67.159.2032026-03-19 → 2026-03-26 · 2 obs

● 2026-03-19 21:04:48
● 2026-03-26 21:34:44

●A2606:4700:3032::6815:59862026-03-19 → 2026-03-26 · 2 obs

● 2026-03-19 21:04:48
● 2026-03-26 21:34:44

●A2606:4700:3033::ac43:9fcb2026-03-19 → 2026-03-26 · 2 obs

● 2026-03-19 21:04:48
● 2026-03-26 21:34:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
chefclearance.com	walt.ns.cloudflare.com, ashley.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.192.71

NS records: walt.ns.cloudflare.com, ashley.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for chefclearance.com (unsigned zone)

⏱️ Timing

Total: 137ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.89.134, 172.67.159.203`
AAAA	2	`2606:4700:3032::6815:5986, 2606:4700:3033::ac43:9fcb`
NS	2	`ashley.ns.cloudflare.com, walt.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`ashley.ns.cloudflare.com dns.cloudflare.`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

chefclearance.com refers to four IP numbers: 2606:4700:3032::6815:5986, 2606:4700:3033::ac43:9fcb, 104.21.89.134 and 172.67.159.203.

Other host names, for instance arcticaccesscil.org, thomas.engineering, www.(0x6e756465)(0x72656474756265).com, 0oepci2.686785.com and 17tgame.com share IP numbers with chefclearance.com.

Name Servers

chefclearance.com's delegation uses two name servers: ashley.ns.cloudflare.com and walt.ns.cloudflare.com.

chefclearance.com uses the same name server setup as other domains, such as adultiop.com, dynamicis.co.uk, xn--hjseng-bya.dk, mrtyremotorsport.com and daniematheus.com.

chefclearance.com at least partially shares name servers with other domains, including comparadorluz.com, killcam.tv, themortgagemaven.com, alvinsim.com and septobot.com.

These name servers are commonly used together with the name servers kim.ns.cloudflare.com, neil.ns.cloudflare.com, henrik.ns.cloudflare.com and tom.ns.cloudflare.com.

Host names with six IP numbers:

ashley.ns.cloudflare.com points to 2606:4700:50::adf5:3a47, 2803:f800:50::6ca2:c047, 2a06:98c1:50::ac40:2047, 108.162.192.71, 172.64.32.71 and 173.245.58.71.

walt.ns.cloudflare.com points to 2606:4700:58::adf5:3b94, 2803:f800:50::6ca2:c194, 2a06:98c1:50::ac40:2194, 108.162.193.148, 172.64.33.148 and 173.245.59.148.

chefclearance.com - robtex.com