Skip to content

Hostname

mytime.de

Last fetched

mytime.de resolves to 78.138.70.119, announced in 78.138.64.0/19 by PLUSSERVER-ASN1 - PlusServer GmbH in DE. mytime.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 · mytime.deRouting diversity1.5/10Peering density6.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/mytime.de

Resolution chain

IPv6 resolution

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

Attribution

plusserver

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for mytime.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
beta.mytime.de
content.mytime.de
firmenservice.mytime.de
gutschein.mytime.de
info.mytime.de
newsletter.mytime.de
partner.mytime.de
pimcore.mytime.de
portal.mytime.de
pwgbwf.mytime.de
rast.mytime.de
shop.mytime.de

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

  • carp.emsnet.de
  • b.ns14.net

MX records

  • fallback01.omg.de
  • mailgate01.omg.de

SPF policy

  • ip: 109.239.192.0/20
  • a: mytime.de
  • mx: mytime.de
  • a: avrelay2.omg.de
  • ip: 80.228.251.33
  • ip: 80.237.192.172
  • ip: 80.237.192.176
  • ip: 80.237.192.180
  • ip: 80.237.192.182
  • ip: 80.237.216.54
  • ip: 80.237.216.56
  • ip: 87.230.11.52
  • ip: 92.51.184.70
  • ip: 92.51.185.162
  • ip: 92.51.185.164

Threat-feed evidence

History

Related pages

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