Skip to content

Hostname

aurednik.de

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

plusserver

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for aurednik.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
0ikfo8.aurednik.de
ai.aurednik.de
autodiscover.aurednik.de
dev.aurednik.de
devai.aurednik.de
exchange01.aurednik.de
mail.aurednik.de
newsletter.aurednik.de
shop.aurednik.de
tpk6.aurednik.de
vpn.aurednik.de
vpn2.aurednik.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

  • ns3.stratoserver.net
  • ns4.stratoserver.net

MX records

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

SPF policy

  • include: spf.hornetsecurity.com
  • include: spf.protection.outlook.com
  • include: _spf.strato.com
  • include: spf.dc-cluster.de
  • include: k44r09.meinserver.io
  • ip: 195.30.84.232
  • ip: 80.147.0.98
  • ip: 80.153.129.97

Threat-feed evidence

History

Related pages

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