Skip to content

Hostname

e-elixir.mk

Last fetched

e-elixir.mk resolves to 188.40.132.124, announced in 188.40.0.0/16 by HETZNER-AS - Hetzner Online GmbH in DE. e-elixir.mk 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 · e-elixir.mkRouting diversity2.4/10Peering density8.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/e-elixir.mk

Resolution chain

IPv6 resolution

No AAAA record for e-elixir.mk is recorded in WhisperGraph.

Attribution

hetzner

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for e-elixir.mk. 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
autodiscover.e-elixir.mk
cpanel.e-elixir.mk
cpcalendars.e-elixir.mk
cpcontacts.e-elixir.mk
dev.e-elixir.mk
elixir.e-elixir.mk
mail.e-elixir.mk
srv.e-elixir.mk
webdisk.e-elixir.mk
webmail.e-elixir.mk
www.e-elixir.mk

Showing 11 of 13. 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

  • ns1.s05.global-net.com.mk
  • ns2.s05.global-net.com.mk

MX records

  • e-elixir.mk

SPF policy

  • a: e-elixir.mk
  • mx: e-elixir.mk
  • include: relay.mailchannels.net
  • ip: 135.181.229.233
  • ip: 136.243.101.181
  • ip: 142.132.206.228
  • ip: 162.55.7.59
  • ip: 188.40.132.124
  • ip: 49.12.132.164
  • ip: 88.198.7.246

Threat-feed evidence

History

Related pages

Pivot from e-elixir.mk 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: "e-elixir.mk"})-[: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.