Skip to content

Hostname

saarbahn.de

Last fetched

saarbahn.de resolves to 185.104.207.82, announced in 185.104.204.0/22 by INTERSAAR-AS - intersaar GmbH in DE. saarbahn.de is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · saarbahn.deRouting diversity1.5/10Peering density6.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/saarbahn.de

Resolution chain

IPv6 resolution

No AAAA record for saarbahn.de is recorded in WhisperGraph.

Attribution

intersaar

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for saarbahn.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
eticket.saarbahn.de
reiseinfo.saarbahn.de
tv.saarbahn.de
tvapi.saarbahn.de
www.saarbahn.de

Showing 5 of 5 subdomains (5 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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns1.tec-saar.de
  • ns2.tec-saar.de
  • ns3.tec-saar.de

MX records

  • tecmxp01.tec-saar.de
  • tecmxp02.tec-saar.de

SPF policy

  • ip: 212.18.200.105/32
  • ip: 212.18.200.106/32
  • ip: 178.250.120.120/32
  • ip: 178.250.120.121/32
  • ip: 178.250.120.122/32
  • ip: 178.250.120.30/32
  • ip: 178.250.120.31/32
  • ip: 185.104.204.74/32
  • a: saarbahn.de
  • mx: saarbahn.de
  • a: bl02-05.saarbruecken.de
  • a: bl02-06.saarbruecken.de

Threat-feed evidence

History

Related pages

Pivot from saarbahn.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: "saarbahn.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 20

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