Skip to content

Hostname

madwise.si

Last fetched

madwise.si resolves to 91.240.216.84, announced in 91.240.216.0/24 by OPTIMUS-AS - Optimus IT d.o.o. in SI. madwise.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 · madwise.siRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/madwise.si

Resolution chain

IPv6 resolution

No AAAA record for madwise.si is recorded in WhisperGraph.

Attribution

optimus it

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for madwise.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
ai-nov-odlocevalec-o-vidnosti.madwise.si
ai-ready-spletne-strani.madwise.si
ai-video-produkcija.madwise.si
alpha-ns.madwise.si
alpha.madwise.si
beta-ns.madwise.si
beta.madwise.si
branding-v-dobi-ai.madwise.si
cpanel.madwise.si
cpcalendars.madwise.si
cpcontacts.madwise.si
delta.madwise.si

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

  • rns7.neoserv.si
  • rns8.neoserv.si

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: _spf.google.com
  • include: _spf.jupiter.salesmanago.pl
  • a: madwise.si
  • mx: madwise.si
  • include: _spf.mail-neoserv.si
  • ip: 91.240.216.82
  • ip: 91.240.216.84
  • ip: 91.240.216.86

Threat-feed evidence

History

Related pages

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