Hostname
wenn.com
Last fetched
wenn.com resolves to 31.43.160.6, announced in 31.43.160.0/24 by AMAZON-02 - Amazon.com, Inc. in NL. wenn.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
- 31.43.160.6
31.43.160.0/24 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 31.43.161.6
31.43.161.0/24 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
IPv6 resolution
No AAAA record for wenn.com is recorded in WhisperGraph.
Attribution
amazon com
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- privacy service provided by withheld for privacy ehf
- Contact emails
- d39bf64cb16c4c4e91a5621dc570d530.protect@whoisguard.com, 92c0709556f84ced89949bee9957c10c.protect@withheldforprivacy.com, wenn.com@myprivacy.net
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
- pns62.cloudns.com
- pns61.cloudns.net
- pns63.cloudns.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- pns64.cloudns.uk
MX records
- wenn-com.mail.protection.outlook.com
SPF policy
- ip: 69.33.241.120/29
- ip: 66.192.194.16/29
- ip: 89.187.64.160/28
- ip: 37.157.37.224/29
- ip: 91.228.115.6/29
- ip: 91.239.125.88/29
- include: spf.protection.outlook.com
- mx: wenn.com
- include: _spf.wetransfer.com
- include: _spf.mailersend.net
- include: servers.mcsv.net
- include: sendgrid.net
- ip: 2a01:c0:2:209:0:0:0:10
Threat-feed evidence
History
Related pages
Pivot from wenn.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: "wenn.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.