Skip to content

Hostname

delko.si

Last fetched

delko.si resolves to 104.21.58.79, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. delko.si 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 · delko.siRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/delko.si

Resolution chain

IPv6 resolution

Attribution

webtasy

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for delko.si. 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
akcija.delko.si
cdn.delko.si
cpanel.delko.si
cpcalendars.delko.si
cpcontacts.delko.si
datoteke.delko.si
de.delko.si
edit.delko.si
files.delko.si
gpbaterije.delko.si
help.delko.si
magento1.delko.si

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

Mail and authentication

Nameservers

  • ben.ns.cloudflare.com
  • jean.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
  • cdns1.controlpanel.si
  • cdns2.controlpanel.si

MX records

  • mail.delko.si

SPF policy

  • include: _spf.controlpanel.si
  • a: delko.si
  • mx: delko.si
  • ip: 178.216.62.194

Threat-feed evidence

History

Related pages

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