Hostname
jeffbuckley.com
Last fetched
jeffbuckley.com resolves to 104.21.19.37, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. jeffbuckley.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.21.19.37
104.21.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.184.243
172.67.176.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:30
- Registrant organisation
- perfect privacy,
- Contact emails
- gu5fd7482fb@namesecureprivatename.com, hk8yb8473k9@nameprivacy.com, jc3ms32x63d@nameprivacy.com, k94um97d5sp@namesecureprivatename.com, nw6ds4ty7rc@namesecureprivatename.com, pj5cp99x2rb@namesecureprivatename.com, q92um8cy6jn@myprivatename.com, qh7j445r3qn@nameprivacy.com, ru8uy7yh3v5@namesecureprivatename.com, ur5uj2rt86j@nameprivacy.com, vv3c373j6s8@namesecureprivatename.com, xk3em69h7e3@myprivatename.com, xs64k9xb8ey@namesecureprivatename.com, yd69u35w948@namesecureprivatename.com, zg3av7bx5a8@namesecureprivatename.com
Subdomains
Showing 2 of 2 subdomains (2 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ashley.ns.cloudflare.com
- vasilii.ns.cloudflare.com
MX records
- smtp.google.com
- cpanel-mail01.digitalwest.net
SPF policy
- ip: 72.29.168.16/28
- ip: 72.29.183.96/27
- mx: jeffbuckley.com
Threat-feed evidence
History
Related pages
Pivot from jeffbuckley.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "jeffbuckley.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.