Skip to content

Hostname

weka.de

Last fetched

weka.de resolves to 194.15.167.15, announced in 194.15.167.0/24 by MNET-AS - M-net Telekommunikations GmbH in DE. weka.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 · weka.deRouting diversity1.5/10Peering density8.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/weka.de

Resolution chain

IPv6 resolution

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

Attribution

net telekommunikations

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for weka.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
am.weka.de
arbeitsschutz.weka.de
ausschreibentest.weka.de
autoren.weka.de
bau.weka.de
cdnlernen.weka.de
ebook.weka.de
emailabfrage.weka.de
faq.weka.de
faq2019.weka.de
forms.weka.de
handel.weka.de

Showing 12 of 45. 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.udag.de
  • ns.udag.net
  • ns.udag.org

MX records

  • mx10.weka.com
  • mx20.weka.com
  • mx30.weka.com

SPF policy

  • ip: 194.15.166.96/32
  • include: spf.protection.outlook.com
  • include: agenturserver.de
  • include: inxserver.de
  • mx: weka.de
  • include: spf1.weka.de
  • include: 4709981.spf01.hubspotemail.net

Threat-feed evidence

History

Related pages

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