Hostname
benaissance.com
Last fetched
benaissance.com resolves to 198.74.62.112, announced in 198.74.56.0/21 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. benaissance.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
- 198.74.62.112
198.74.56.0/21 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Cedar Knolls, US
IPv6 resolution
No AAAA record for benaissance.com is recorded in WhisperGraph.
Attribution
akamai
ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- coco development
- Contact emails
- john.jenkins@benaissance.com, qw9bv398883@networksolutionsprivateregistration.com, 1d935adf-b75f-487a-a39f-14b626b7bbe5@identity-protect.org, 347f6c87-c2f7-4c42-a0c5-3ac4083df7d7@identity-protect.org, 99b41af8-a386-42ea-a3d0-c939ef5baa9a@identity-protect.org, 99c991ed-9345-43c7-b591-59a5f6f70987@identity-protect.org, d4182691-afc8-4a14-9638-9859b99eb4cd@identity-protect.org, df553765-da15-49eb-a941-ed343d510690@identity-protect.org
Subdomains
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
Sample outbound links
Mail and authentication
Nameservers
- ns1-02.azure-dns.com
- ns4-02.azure-dns.info
- ns4-05.azure-dns.info
- ns2-02.azure-dns.net
- ns3-02.azure-dns.org
MX records
- us-smtp-inbound-1.mimecast.com
- us-smtp-inbound-2.mimecast.com
SPF policy
- mx: benaissance.com
- include: us._netblocks.mimecast.com
- include: auth.msgapp.com
- include: _spf.salesforce.com
- include: spf.dynect.net
Threat-feed evidence
History
Related pages
Pivot from benaissance.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: "benaissance.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.