Hostname
bbw-leipzig.de
Last fetched
bbw-leipzig.de resolves to 1 IPv4 address operated by AS24940 in DE.
Nutrition Label
Resolution chain
bbw-leipzig.de resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 176.9.127.68 | 176.9.0.0/16 | AS24940 | — | DE |
WHOIS identity
No WHOIS records are currently associated with bbw-leipzig.de in WhisperGraph.
Subdomains
26 observed subdomains of bbw-leipzig.de.
Showing 17 of 26. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from bbw-leipzig.de in the public web crawl.
90 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
38 SPF mechanisms authorising senders for bbw-leipzig.de.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.kundenserver.de |
| SPF_INCLUDE | _spf.perfora.net |
| SPF_INCLUDE | spf.hornetsecurity.com |
| SPF_IP | 109.239.48.0/20 |
| SPF_IP | 134.119.0.0/17 |
| SPF_IP | 134.119.0.0/24 |
| SPF_IP | 134.119.128.0/19 |
| SPF_IP | 134.119.160.0/20 |
| SPF_IP | 134.119.224.0/19 |
| SPF_IP | 134.119.228.0/24 |
| SPF_IP | 141.0.16.0/21 |
| SPF_IP | 176.221.40.0/21 |
| SPF_IP | 185.21.100.0/22 |
| SPF_IP | 188.93.8.0/21 |
| SPF_IP | 195.145.155.2 |
| SPF_IP | 2001:1520:a:0:0:0:0:0/56 |
| SPF_IP | 213.131.239.224/28 |
| SPF_IP | 213.203.225.128/27 |
| SPF_IP | 217.13.73.0/24 |
| SPF_IP | 2a00:1158:0:300::/56 |
| SPF_IP | 2a00:1158:400:1::0/120 |
| SPF_IP | 2a00:1158:5::/48 |
| SPF_IP | 37.200.96.0/21 |
| SPF_IP | 46.252.16.0/20 |
| SPF_IP | 62.67.200.0/24 |
| SPF_IP | 77.91.232.0/21 |
| SPF_IP | 80.67.16.0/20 |
| SPF_IP | 81.209.187.0/24 |
| SPF_IP | 92.204.236.0/24 |
| SPF_IP | 92.204.239.0/24 |
| SPF_IP | 92.204.33.0/24 |
| SPF_IP | 92.204.37.0/24 |
| SPF_IP | 92.204.43.0/24 |
| SPF_IP | 92.204.55.0/24 |
| SPF_IP | 92.204.58.0/24 |
| SPF_IP | 93.180.152.0/21 |
| SPF_IP | 93.187.232.0/21 |
| SPF_MX | bbw-leipzig.de |
Related pages
Pivot deeper into the graph from bbw-leipzig.de.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "bbw-leipzig.de"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.