Skip to content

Hostname

nayoki.de

Last fetched

nayoki.de resolves to 85.214.155.74, announced in 85.214.0.0/15 by STRATO - Strato GmbH in DE. nayoki.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 · nayoki.deRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/nayoki.de

Resolution chain

IPv6 resolution

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

Attribution

strato

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for nayoki.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
adgen.nayoki.de
alerthub.nayoki.de
avada.nayoki.de
bmw.nayoki.de
cdn777.nayoki.de
cdnpull.nayoki.de
dashboard.nayoki.de
doku.nayoki.de
feeds.nayoki.de
iqos.nayoki.de
kongresshotel.nayoki.de
mail.nayoki.de

Showing 12 of 25. 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.second-ns.com
  • ns3.second-ns.de
  • ns1.your-server.de

MX records

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

SPF policy

  • include: spf-de.emailsignatures365.com
  • include: spf.hornetsecurity.com
  • include: spf.protection.outlook.com
  • include: spf.easybill-mail.de

Threat-feed evidence

History

Related pages

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