Hostname
yumsugar.com
Last fetched
yumsugar.com resolves to 104.18.26.182, announced in 104.18.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. yumsugar.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.18.26.182
104.18.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.27.182
104.18.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.21.1.237
104.21.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.152.149
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:1781
- Registrant organisation
- domain discreet privacy service attn: yumsugar.com
- Contact emails
- 02afd2140a16123308216547913a64e8@domaindiscreet.com, 765b97e90a28fd0a777d6a6fd31c161f@domaindiscreet.com, yumsugar.com@namebrightprivacy.com, support@dropcatch.com, 142ae2e0-4943-4b5f-8b52-c7994b7b1008@identity-protect.org, 3ff6fb63-7aac-4539-ae5b-3b3acf381fbd@identity-protect.org, 9812dec8-6546-41b7-b951-a640eb598e72@identity-protect.org, aeed4227-335a-442a-8ab6-c973355242e2@identity-protect.org, owner-8965936@yumsugar.com.whoisprivacyservice.org, owner-9496669@yumsugar.com.whoisprivacyservice.org, owner@yumsugar.com.whoisprivacyservice.org
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
- melina.ns.cloudflare.com
- roman.ns.cloudflare.com
- rory.ns.cloudflare.com
- tegan.ns.cloudflare.com
Threat-feed evidence
History
Related pages
Pivot from yumsugar.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: "yumsugar.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.