Hostname
vonmaur.com
Last fetched
vonmaur.com resolves to 104.81.116.249, announced in 104.81.96.0/19 by AKAMAI-AS - Akamai Technologies, Inc. in PL. vonmaur.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.81.116.249
104.81.96.0/19 · AKAMAI-AS - Akamai Technologies, Inc. · Warsaw, PL
- 23.201.181.209
23.201.160.0/19 · AKAMAI-AS - Akamai Technologies, Inc. · Secaucus, US
- 23.201.247.121
23.201.240.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.212.215.133
23.212.208.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.45.105.117
23.45.96.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.67.139.120
23.67.128.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for vonmaur.com is recorded in WhisperGraph.
Attribution
akamai
ORIGIN_AS
WHOIS identity
- Registrar
- registrar:network solutions, llc.
- Registrant organisation
- ******** ******** (see notes section below on how to view unmasked data)
- Contact emails
- ********@*****.***, jmoffitt@vonmaur.com, wvarilek@vonmaur.com
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
- a1-214.akam.net
- a12-65.akam.net
- a2-66.akam.net
- a22-67.akam.net
- a3-64.akam.net
- a5-65.akam.net
MX records
- mxa-00592601.gslb.pphosted.com
- mxb-00592601.gslb.pphosted.com
SPF policy
- include: res.cisco.com
- include: spf.protection.outlook.com
- include: spf-00592601.pphosted.com
- mx: vonmaur.com
- ip: 192.190.137.195
- ip: 34.197.1.101
- ip: 34.198.111.171
Threat-feed evidence
History
Related pages
Pivot from vonmaur.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: "vonmaur.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.