Skip to content

Hostname

luckia.hr

Last fetched

luckia.hr resolves to 104.18.2.181, announced in 104.18.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. luckia.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 · luckia.hrRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.0/10canon.whisper.security/host/luckia.hr

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
registrar:posluh hosting d.o.o.
Registrant organisation
major internacional d.o.o.
Contact emails
darko@it-grupa.hr, ivan@it-grupa.hr

Subdomains

Subdomain
0a7641c6680e.luckia.hr
autodiscover.luckia.hr
cloud.luckia.hr
mail.luckia.hr
www.luckia.hr

Showing 5 of 6. 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

  • ajay.ns.cloudflare.com
  • desiree.ns.cloudflare.com
  • 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

  • _dc-mx.0a7641c6680e.luckia.hr
  • route1.mx.cloudflare.net
  • route2.mx.cloudflare.net
  • route3.mx.cloudflare.net
  • mxa.eu.mailgun.org
  • mxb.eu.mailgun.org

SPF policy

  • include: 21l73oshk.spf.checkpoint-spf.com
  • mx: luckia.hr
  • a: mail.vodatel.hr
  • include: mailgun.org
  • ip: 217.14.208.60
  • ip: 217.14.208.61
  • ip: 82.193.222.226

Threat-feed evidence

History

Related pages

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