Skip to content

Hostname

kucerave.sk

Last fetched

kucerave.sk resolves to 185.102.21.26, announced in 185.102.21.0/24 by ONE-NETWORK - dogado GmbH in DE. kucerave.sk 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 · kucerave.skRouting diversity3.0/10Peering density5.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint9.2/10canon.whisper.security/host/kucerave.sk

Resolution chain

Attribution

dogado

ORIGIN_AS

WHOIS identity

Registrar
registrar:webglobe, a.s.
Registrant organisation
cardoso s.r.o.

Subdomains

Subdomain
lh.kucerave.sk
mailin1.kucerave.sk
mailin2.kucerave.sk
wildcard.kucerave.sk
www.kucerave.sk

Showing 5 of 5 subdomains (5 per page).

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

  • emely.ns.cloudflare.com
  • jaime.ns.cloudflare.com
  • ns4.hostcreators.eu
  • ns1.dnsbackup.net
  • ns2.dnsbackup.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
  • ns1.hostcreators.sk
  • ns2.hostcreators.sk
  • ns3.hostcreators.sk
  • ns1.nameserver.sk
  • ns2.nameserver.sk

MX records

  • smtp.google.com
  • mailin.mx-hub.cz
  • mailin.mx-hub.eu
  • mailin.mx-hub.net
  • mx1.hostcreators.sk
  • mx2.hostcreators.sk
  • mailin.mx-hub.sk

SPF policy

  • include: _spf.hostcreators.sk
  • a: kucerave.sk
  • mx: kucerave.sk
  • include: _spf.nameserver.sk

Threat-feed evidence

History

Related pages

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