Skip to content

Hostname

mydays.de

Last fetched

mydays.de resolves to 13.227.192.101, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. mydays.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 · mydays.deRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/mydays.de

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for mydays.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
aktion.mydays.de
b2b-test.mydays.de
b2b.mydays.de
cdn.mydays.de
click.mydays.de
connex.mydays.de
emotion.mydays.de
invent.mydays.de
kundenportal.mydays.de
kundenservice.mydays.de
legacy.mydays.de
magazin.mydays.de

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

  • ns-247.awsdns-30.com
  • ns-661.awsdns-18.net
  • ns-1178.awsdns-19.org
  • ns-2041.awsdns-63.co.uk

MX records

  • mx01.hornetsecurity.com
  • mx02.hornetsecurity.com
  • mx03.hornetsecurity.com
  • mx04.hornetsecurity.com

SPF policy

  • include: spf.hornetsecurity.com
  • include: iagent-ondemand._spf.novomind.com
  • include: spf.protection.outlook.com
  • include: _spf.salesforce.com
  • a: mydays.de
  • mx: mydays.de
  • include: spf.cluster-team.net
  • ip: 188.65.77.144

Threat-feed evidence

History

Related pages

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