`clearlyfuzzy.com`

DNSSEC	⚠️ Not signed
A	162.241.218.88^{🇺🇸 ORACLE-OCI-31898162.241.216.0/22 Google}
		PTR	`box5550.bluehost.com`
NS	`ns1.bluehost.com` ⭐
		A	162.159.24.80^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.bluehost.com`
NS	`ns2.bluehost.com`
		A	162.159.25.175^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.bluehost.com`
MX	`mail.clearlyfuzzy.com` ⭐
		A	162.241.218.88^{🇺🇸 ORACLE-OCI-31898162.241.216.0/22 Google}
			PTR	`box5550.bluehost.com`
MX	`clearlyfuzzy.com`⁽¹⁰⁾
		A	162.241.218.88^{🇺🇸 ORACLE-OCI-31898162.241.216.0/22 Google}
			PTR	`box5550.bluehost.com`
TXT	`v=spf1 ip4:162.241.218.88 a mx include:websitewelcome.com ~all`
SOA	`ns1.bluehost.com`root@box5550.bluehost.com 2023-07-14 #9

`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

MX for

clearlyfuzzy.com

Same first word

clearlyfuzzy.com

DNS History

5 records (5 active, 0 former)

●NSns1.bluehost.com2026-02-25 → 2026-03-23 · 2 obs

● 2026-02-25 16:44:06
● 2026-03-23 03:41:12

●NSns2.bluehost.com2026-02-25 → 2026-03-23 · 2 obs

● 2026-02-25 16:44:06
● 2026-03-23 03:41:12

●MXclearlyfuzzy.com2026-02-25 → 2026-03-23 · 2 obs

● 2026-02-25 16:44:06
● 2026-03-23 03:41:12

●MXmail.clearlyfuzzy.com2026-02-25 → 2026-03-23 · 2 obs

● 2026-02-25 16:44:06
● 2026-03-23 03:41:12

●A162.241.218.882026-02-25 → 2026-03-23 · 2 obs

● 2026-02-25 16:44:06
● 2026-03-23 03:41:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, j.gtld-servers.net, f.gtld-servers.net, b.gtld-servers.net...	-
clearlyfuzzy.com	ns1.bluehost.com, ns2.bluehost.com	2 records

✅ Authoritative Response

Server:162.159.24.80

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for clearlyfuzzy.com (unsigned zone)

⏱️ Timing

Total: 290ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`162.241.218.88`
NS	2	`ns1.bluehost.com, ns2.bluehost.com`
MX	2	`clearlyfuzzy.com (pri: 10), mail.clearlyfuzzy.com (pri: 0)`
TXT	1	`v=spf1 ip4:162.241.218.88 a mx include:w`
SOA	1	`ns1.bluehost.com root.box5550.bluehost.c`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.bluehost.com, ns2.bluehost.com)

Analysis

Mail Server Role

clearlyfuzzy.com serves as the mail server for clearlyfuzzy.com.

mail.clearlyfuzzy.com is commonly used as a mail server with clearlyfuzzy.com.

IP Addresses

clearlyfuzzy.com resolves to a single IP address: 162.241.218.88.

Other host names including kimberlybravo.com, petermallo.com, mail.zowiemedia.net, mail.(0x626f6f62)ustingbabes.com and mail.everythingagro.com share IP numbers with clearlyfuzzy.com.

Name Servers

clearlyfuzzy.com's delegation uses two name servers, ns1.bluehost.com and ns2.bluehost.com.

clearlyfuzzy.com shares the same name server setup as other domains, for example aquasim.com, wgmagazine.com, curepainful(0x736578).com, royalpettoys.com and alkebuware.com.

clearlyfuzzy.com partially shares its name servers with other domains, for example t007.com and towdude.com.

Host names with a single IP:

ns1.bluehost.com points to 162.159.24.80.

ns2.bluehost.com points to 162.159.25.175.

Mail Servers

Two mail servers handle clearlyfuzzy.com: clearlyfuzzy.com and mail.clearlyfuzzy.com.

Host names with a single IP:

- clearlyfuzzy.com points to 162.241.218.88

- mail.clearlyfuzzy.com points to 162.241.218.88

Host names that point to 162.241.218.88: clearlyfuzzy.com and mail.clearlyfuzzy.com

clearlyfuzzy.com - robtex.com