Skip to content

Hostname

esky.hr

Last fetched

esky.hr resolves to 2.18.64.25, announced in 2.18.64.0/24 by AKAMAI-ASN1 - Akamai International B.V. in DE. esky.hr 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 · esky.hrRouting diversity1.5/10Peering density9.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.6/10canon.whisper.security/host/esky.hr

Resolution chain

IPv6 resolution

No AAAA record for esky.hr is recorded in WhisperGraph.

Attribution

akamai international

ORIGIN_AS

WHOIS identity

Registrar
registrar:orbis d.o.o.
Registrant organisation
esky.pl społka akcyjna
Contact emails
domreg@101domain.com

Subdomains

Subdomain
app.esky.hr
blackfriday.esky.hr
blog.esky.hr
etm.esky.hr
go.esky.hr
mail.esky.hr
nl.esky.hr
popusti.esky.hr
secure.esky.hr
traveltalks.esky.hr
wallet.esky.hr
wildcard.esky.hr

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

  • a1-156.akam.net
  • a24-67.akam.net
  • a4-64.akam.net
  • a5-65.akam.net
  • a6-66.akam.net
  • a7-67.akam.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • smtp.google.com

SPF policy

  • include: _spf.google.com
  • include: spf.ipresso.pl
  • include: _spf.emaillabs.net.pl
  • ip: 148.251.32.220
  • ip: 91.227.120.120

Threat-feed evidence

History

Related pages

Pivot from esky.hr 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: "esky.hr"})-[: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.