Skip to content

Hostname

kymco.de

Last fetched

kymco.de resolves to 46.251.251.148, announced in 46.251.251.0/24 by IP-PROJECTS - Michael Sebastian Schinzel trading as IP-Projects GmbH & Co. KG in DE. kymco.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 · kymco.deRouting diversity1.5/10Peering density6.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.5/10canon.whisper.security/host/kymco.de

Resolution chain

IPv6 resolution

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

Attribution

michael sebastian schinzel trading ip projects

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for kymco.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
dev.kymco.de
mail.kymco.de
mail2.kymco.de
mail3.kymco.de
mail4.kymco.de
test.kymco.de
www.kymco.de

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

  • ns3.edns.de
  • ns4.edns.de
  • ns1.i-comm.de
  • ns3.ip-projects.de
  • ns4.ip-projects.de
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • trustmail1.circular.de
  • mail.kymco.de
  • mail2.kymco.de
  • mail3.kymco.de
  • mail4.kymco.de

Threat-feed evidence

History

Related pages

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