Skip to content

Hostname

bora.fi

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

ovh

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for bora.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
autoconfig.bora.fi
autodiscover.bora.fi
cpanel.bora.fi
cpcalendars.bora.fi
cpcontacts.bora.fi
ipv6.bora.fi
mail.bora.fi
webdisk.bora.fi
webmail.bora.fi
www.bora.fi

Showing 10 of 10 subdomains (10 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

  • dns1.nida.fi
  • dns2.nida.fi
  • ns1.z.fi
  • ns2.z.fi

MX records

  • bora.fi
  • nv2.nida.fi

SPF policy

  • a: bora.fi
  • mx: bora.fi
  • a: mail.bora.fi
  • a: smtp.bora.fi
  • a: mail2.nida.fi
  • a: mail4.nida.fi
  • a: nv2.nida.fi
  • ip: 162.19.10.100
  • ip: 2001:41d0:25f:6400:0:0:0:0

Threat-feed evidence

History

Related pages

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