Skip to content

Hostname

schickort.de

Last fetched

schickort.de resolves to 75.2.24.103, announced in 75.2.16.0/20 by AMAZON-02 - Amazon.com, Inc. in US. schickort.de is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:55:24 GMT
Last seen on a feed
Thu, 17 Sep 2026 00:15:21 GMT

Nutrition Label

WHISPER CANON · schickort.deRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/schickort.de

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for schickort.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
m.schickort.de
www.schickort.de

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

  • ns43.domaincontrol.com
  • ns44.domaincontrol.com
  • 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

  • mx.c2.icoremail.net
  • mx2.c2.icoremail.net
  • mx3.c2.icoremail.net
  • schickort-de.mail.protection.outlook.com

SPF policy

  • include: mailgun.org

Threat-feed evidence

History

Related pages

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