Skip to content

Hostname

tyresystem.de

Last fetched

tyresystem.de resolves to 109.235.228.146, announced in 109.235.224.0/21 by TELENET-AS - SWU TeleNet GmbH in DE. tyresystem.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 · tyresystem.deRouting diversity1.5/10Peering density6.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/tyresystem.de

Resolution chain

IPv6 resolution

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

Attribution

swu telenet

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for tyresystem.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
api.tyresystem.de
ftp.tyresystem.de
mail.tyresystem.de
partnerdays.tyresystem.de
preview.tyresystem.de
www.tyresystem.de

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

  • ns49.domaincontrol.com
  • ns50.domaincontrol.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: mail.zendesk.com
  • a: backend-exchange.rsu-hausverwalter.de
  • a: mail2.rsu-hausverwalter.de
  • a: tyresystem.de
  • mx: tyresystem.de
  • a: mail.tyresystem.de

Threat-feed evidence

History

Related pages

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