Hostname
openmesh.com
Last fetched
openmesh.com resolves to 104.71.185.87, announced in 104.71.176.0/20 by AKAMAI-AS - Akamai Technologies, Inc. in US. openmesh.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.71.185.87
104.71.176.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · New York, US
- 23.197.133.139
23.197.128.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.197.137.35
23.197.128.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.37.42.2
23.37.32.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.37.55.22
23.37.48.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.57.45.182
23.57.32.0/19 · AKAMAI-AS - Akamai Technologies, Inc. · Bengaluru, IN
- 23.63.116.117
23.63.112.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Berlin, DE
IPv6 resolution
Attribution
akamai
ORIGIN_AS
WHOIS identity
- Registrar
- iana:299
- Registrant organisation
- on behalf of openmesh.com owner
- Contact emails
- domains@kaseya.com, xe84k28q4ru@networksolutionsprivateregistration.com, 1b41898d-6afd-4b6d-8d4c-e43bd256a028@identity-protect.org, a7cf96ab-4fab-4619-9790-49f62ade1b78@identity-protect.org, c8851897-98c7-4db8-808b-4332b035b8a0@identity-protect.org, e12d4678-bd94-4b6c-8d3b-0067424af032@identity-protect.org, owner-10258395@openmesh.com.whoisprivacyservice.org, owner-2609337@openmesh.com.whoisprivacyservice.org, owner-5065519@openmesh.com.whoisprivacyservice.org, owner-9202730@openmesh.com.whoisprivacyservice.org, owner-9686568@openmesh.com.whoisprivacyservice.org, owner-9731396@openmesh.com.whoisprivacyservice.org, owner-9791064@openmesh.com.whoisprivacyservice.org
Subdomains
Showing 3 of 3 subdomains (3 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
- a1-24.akam.net
- a10-65.akam.net
- a22-66.akam.net
- a28-67.akam.net
- a5-64.akam.net
- a9-65.akam.net
MX records
- us-smtp-inbound-1.mimecast.com
- us-smtp-inbound-2.mimecast.com
SPF policy
- include: _spf.google.com
- include: us._netblocks.mimecast.com
- include: mktomail.com
- include: _spf.salesforce.com
Threat-feed evidence
History
Related pages
Pivot from openmesh.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: "openmesh.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.