Skip to content

Hostname

kia.de

Last fetched

kia.de resolves to 91.217.230.137, announced in 91.217.230.0/24 by AUTOEVER-EUROPE - Hyundai AutoEver Europe GmbH in DE. kia.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 · kia.deRouting diversity2.4/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/kia.de

Resolution chain

IPv6 resolution

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

Attribution

hyundai autoever europe

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for kia.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
_tls.kia.de
api.kia.de
apitest.kia.de
as400.kia.de
autodiscover.kia.de
ceed.kia.de
christopherus.kia.de
com.kia.de
confluence.kia.de
datenschutzzentrale.kia.de
dcs.kia.de
dein.kia.de

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

  • a.ns14.net
  • b.ns14.net
  • c.ns14.net
  • d.ns14.net

MX records

  • reply.s13.exacttarget.com
  • mxa-00a94d01.gslb.pphosted.com
  • mxb-00a94d01.gslb.pphosted.com
  • mx1.kia.eu
  • mx2.kia.eu

SPF policy

  • include: spf-00a94d01.pphosted.com
  • include: _spf.salesforce.com
  • mx: kia.de
  • a: ems1.kia.de
  • a: ems2.kia.de
  • a: mail.kiadialog.de
  • ip: 185.106.9.32
  • ip: 185.106.9.33
  • ip: 91.217.230.18
  • ip: 91.217.230.88
  • ip: 91.217.230.89

Threat-feed evidence

History

Related pages

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