Skip to content

Hostname

myschleppapp.de

Last fetched

myschleppapp.de resolves to 104.21.13.4, announced in 104.21.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. myschleppapp.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 · myschleppapp.deRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.6/10canon.whisper.security/host/myschleppapp.de

Resolution chain

IPv6 resolution

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

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for myschleppapp.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.myschleppapp.de
gw.myschleppapp.de
portal.myschleppapp.de
psa3.myschleppapp.de
pw.myschleppapp.de
www.myschleppapp.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

  • ns-507.awsdns-63.com
  • coby.ns.cloudflare.com
  • kim.ns.cloudflare.com
  • ns-958.awsdns-55.net
  • ns-1336.awsdns-39.org
  • ns-1738.awsdns-25.co.uk

MX records

  • myschleppapp-de.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • a: otc-de-spf.mms.t-systems-service.com
  • a: spf-cloud.mms.t-systems-service.com
  • a: myschleppapp.de
  • mx: myschleppapp.de

Threat-feed evidence

History

Related pages

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