Hostname
mannco.store
Last fetched
mannco.store resolves to 104.20.47.36, announced in 104.20.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. mannco.store 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.20.47.36
104.20.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.6.112
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.7.112
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.148.51
172.66.144.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.68.101
172.67.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for mannco.store is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · MAIL_RECEIVER, ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1910
- Registrant organisation
- minelauva holdings
- Contact emails
- 4fb37d983dad4c53adbaf5e66b86498e.protect@whoisguard.com
Subdomains
| Subdomain |
|---|
| cs2ss.mannco.store |
| etsre.mannco.store |
| iuhbfvz.mannco.store |
| monitor.mannco.store |
| zguduvjf.mannco.store |
Showing 5 of 5 subdomains (5 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.
Sample inbound links
Mail and authentication
Nameservers
- leah.ns.cloudflare.com
- lee.ns.cloudflare.com
MX records
- inbound-smtp.us-east-1.amazonaws.com
- 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: amazonses.com
- include: _spf.google.com
- include: spf.mailjet.com
- include: spf.tipalti.com
- include: trustpilotservice.com
Threat-feed evidence
History
Related pages
Pivot from mannco.store 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: "mannco.store"})-[: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.