Skip to content

Hostname

taures.de

Last fetched

taures.de resolves to 51.91.60.123, announced in 51.91.0.0/16 by OVH - OVH SAS in FR. taures.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 · taures.deRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/taures.de

Resolution chain

IPv6 resolution

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

Attribution

ovh

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for taures.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
alvo.taures.de
alvodev.taures.de
atrium.taures.de
ausbildung.taures.de
cat.taures.de
cluster.taures.de
companies-and-tariffs-backend.taures.de
companies-and-tariffs.taures.de
crm.taures.de
dev-cat.taures.de
dev-companies-and-tariffs-backend.taures.de
dev-companies-and-tariffs.taures.de

Showing 12 of 136. View all 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

  • dns103.ovh.net
  • ns103.ovh.net

MX records

  • mxext1.mailbox.org
  • mxext2.mailbox.org
  • mxext3.mailbox.org
  • mxext4.mailbox.org

SPF policy

  • include: _spf.a-fk.de
  • include: spf.softfair.de
  • a: taures.de
  • mx: taures.de
  • include: mailbox.org
  • ip: 195.145.112.226
  • ip: 212.60.228.66

Threat-feed evidence

History

Related pages

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