Hostname
yenko.net
Last fetched
yenko.net resolves to 104.26.2.26, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. yenko.net 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.26.2.26
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.3.26
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.72.165
172.67.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- lillard, charley
- Contact emails
- clill8567@aol.com, supercarregistrysite@gmail.com, sshauger@optonline.net
Subdomains
| Subdomain |
|---|
| beta.yenko.net |
| cpanel.yenko.net |
| cpcalendars.yenko.net |
| cpcontacts.yenko.net |
| mail.yenko.net |
| webdisk.yenko.net |
| webmail.yenko.net |
| www.yenko.net |
Showing 8 of 8 subdomains (8 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
- annalise.ns.cloudflare.com
- rommy.ns.cloudflare.com
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- include: spf.mandrillapp.com
- a: yenko.net
- mx: yenko.net
- ip: 173.236.81.35
- ip: 74.116.1.74
Threat-feed evidence
History
Related pages
Pivot from yenko.net 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: "yenko.net"})-[: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.