Hostname
ybdfinds.com
Last fetched
ybdfinds.com resolves to 104.18.26.96, announced in 104.18.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. ybdfinds.com is listed by 2 threat feeds; reconciled level CRITICAL.
Threat posture
60threat score (procedure-native scale)
CRITICALListed by 2 threat feeds. At least one source recommends blocking.
Categories: Command-and-control
- Threat feeds listing this
- 2
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:50:48 GMT
- Last seen on a feed
- Sun, 13 Sep 2026 00:52:19 GMT
Nutrition Label
Resolution chain
- 104.18.26.96
104.18.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.27.96
104.18.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.21.42.17
104.21.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.155.27
172.67.144.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:146
- Registrant organisation
- domains by proxy,
Subdomains
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
- dilbert.ns.cloudflare.com
- hadlee.ns.cloudflare.com
- ishaan.ns.cloudflare.com
- joselyn.ns.cloudflare.com
- maciej.ns.cloudflare.com
- serenity.ns.cloudflare.com
- tiffany.ns.cloudflare.com
- wesley.ns.cloudflare.com
- ns49.domaincontrol.com
- ns50.domaincontrol.com
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: dc-aa8e722993._spfm.ybdfinds.com
Threat-feed evidence
History
Related pages
Pivot from ybdfinds.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: "ybdfinds.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.