Skip to content

Hostname

podnapisi.net

Last fetched

podnapisi.net resolves to 91.185.203.249, announced in 91.185.192.0/19 by TELEMACH-HOSTING - Telemach Slovenija d.o.o. in SI. podnapisi.net 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 · podnapisi.netRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/podnapisi.net

Resolution chain

IPv6 resolution

Attribution

telemach slovenija

ORIGIN_AS

WHOIS identity

Registrar
iana:303
Registrant organisation
matic kalisnik
Contact emails
gdpr-masking@gdpr-masked.com, hostmaster@unimatrix-one.org, hostmaster@unimatrix.si

Subdomains

Subdomain
ar.podnapisi.net
bg.podnapisi.net
bra.podnapisi.net
cyr.podnapisi.net
de.podnapisi.net
el.podnapisi.net
en.podnapisi.net
fi.podnapisi.net
fr.podnapisi.net
hr.podnapisi.net
hu.podnapisi.net
imap.podnapisi.net

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

  • ns-global.kjsl.com
  • ns1.podnapisi.net
  • ns2.podnapisi.net
  • ns3.podnapisi.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.afraid.org
  • ns2.afraid.org

MX records

  • mx1.podnapisi.net
  • mx1-ipv4.podnapisi.net
  • emx.mail.ru

SPF policy

  • mx: podnapisi.net
  • a: mx-out1.gogo.si
  • a: mx-out2.gogo.si

Threat-feed evidence

History

Related pages

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