Skip to content

Hostname

cinetic21.de

Last fetched

cinetic21.de resolves to 213.144.9.87, announced in 213.144.0.0/19 by TELEMAXX - TelemaxX Telekommunikation GmbH in DE. cinetic21.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 · cinetic21.deRouting diversity1.5/10Peering density7.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/cinetic21.de

Resolution chain

IPv6 resolution

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

Attribution

telemaxx telekommunikation

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for cinetic21.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
10171cluster.cinetic21.de
autodiscover.cinetic21.de
basf-aroma-products.cinetic21.de
basf-mailservice-clone.cinetic21.de
basf-mailservice.cinetic21.de
basf.cinetic21.de
basfintranet.cinetic21.de
cip.cinetic21.de
cmereg.cinetic21.de
commonbasf.cinetic21.de
commonbih.cinetic21.de
dlan.cinetic21.de

Showing 12 of 53. 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

  • ns23.cinetic21.de
  • ns42.cinetic21.de

MX records

  • mailin01.cinetic21.de
  • mailin02.cinetic21.de

SPF policy

  • a: cinetic21.de
  • mx: cinetic21.de
  • ip: 213.144.24.82
  • ip: 213.144.9.201
  • ip: 213.144.9.202
  • ip: 213.144.9.211
  • ip: 213.144.9.212
  • ip: 213.144.9.87
  • ip: 46.237.240.76

Threat-feed evidence

History

Related pages

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