Skip to content

Hostname

proxyconnect.boening.com

Last fetched

proxyconnect.boening.com resolves to 2 IPv4 addresses operated by AS6878 in DE.

Nutrition Label

WHISPER CANON · proxyconnect.boening.comRouting diversity2.4/10Peering density7.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint0.0/10canon.whisper.security/host/proxyconnect.boening.com

Resolution chain

proxyconnect.boening.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
164.30.71.92164.38.196.0/24AS6878—DE
40.114.243.21540.128.0.0/14AS8075MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft CorporationNL

WHOIS identity

No WHOIS records are currently associated with proxyconnect.boening.com in WhisperGraph.

Threat posture

History

Mail and authentication

MX records

SPF policy

4 SPF mechanisms authorising senders for proxyconnect.boening.com.

MechanismTarget
SPF_Aproxyconnect.boening.com
SPF_INCLUDE_spf.anyviz.io
SPF_IP52.233.249.121/32
SPF_MXproxyconnect.boening.com

Related pages

Pivot deeper into the graph from proxyconnect.boening.com.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "proxyconnect.boening.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.