Hostname
bahnreiseladen.de
Last fetched
bahnreiseladen.de resolves to 104.21.69.5, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. bahnreiseladen.de 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.21.69.5
104.21.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.202.37
172.67.192.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for bahnreiseladen.de. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
| Subdomain |
|---|
| acceptatie.bahnreiseladen.de |
| support.bahnreiseladen.de |
| testing.bahnreiseladen.de |
| www.bahnreiseladen.de |
Showing 4 of 4 subdomains (4 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
- tani.ns.cloudflare.com
- terry.ns.cloudflare.com
MX records
- bahnreiseladen-de.mail.protection.outlook.com
- mail.interpulse.nl
- dbs-mta-001.netmatch.nl
- smtp.treinreiswinkel.nl
SPF policy
- ip: 84.41.128.99/32
- a: mail.authsmtp.com
- include: helpscoutemail.com
- include: spf.protection.outlook.com
- mx: bahnreiseladen.de
- include: spf.mtasv.net
- include: sendgrid.net
- a: smtp01.esprittelecom.nl
- a: smtp02.esprittelecom.nl
- include: _datacenter.interpulse.nl
- a: mailoutgoing.swis.nl
- a: hats.nu
- include: eu.mailgun.org
- ip: 2001:888:2085:0:0:0:0:4
- ip: 212.67.182.155
- ip: 82.94.189.99
- ip: 82.94.225.110
- ip: 82.94.225.4
Threat-feed evidence
History
Related pages
Pivot from bahnreiseladen.de 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: "bahnreiseladen.de"})-[: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.