Skip to content

Hostname

nida.fi

Last fetched

nida.fi resolves to 141.95.147.213, announced in 141.95.128.0/17 by OVH - OVH SAS in FR. nida.fi 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 · nida.fiRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.6/10canon.whisper.security/host/nida.fi

Resolution chain

IPv6 resolution

No AAAA record for nida.fi is recorded in WhisperGraph.

Attribution

ovh

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for nida.fi. 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
demo.nida.fi
dns1.nida.fi
dns2.nida.fi
ftp2.nida.fi
isp1.nida.fi
isp2.nida.fi
isp4.nida.fi
mail.nida.fi
mail1.nida.fi
mail2.nida.fi
mail4.nida.fi
mx01.nida.fi

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

  • dns1.nida.fi
  • dns2.nida.fi
  • ns1.z.fi
  • ns2.z.fi
  • dns102.ovh.net
  • ns102.ovh.net

MX records

  • nida.fi
  • nv2.nida.fi
  • mx0.mail.ovh.net
  • mx1.mail.ovh.net
  • mx2.mail.ovh.net
  • mx3.mail.ovh.net

SPF policy

  • ip: 2001:41d0:203:b4b5::/56
  • ip: 2001:41d0:203:c4d5::/56
  • ip: 2001:41d0:25f:6400::/56
  • ip: 141.94.162.181
  • ip: 141.95.147.213
  • ip: 162.19.10.100
  • ip: 188.165.7.3
  • ip: 2001:41d0:1:1b00:188:165:143:3

Threat-feed evidence

History

Related pages

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