Skip to content

Hostname

osheaga.com

Last fetched

osheaga.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. osheaga.com 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 · osheaga.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/osheaga.com

Resolution chain

No IPv4 resolution is recorded for osheaga.com in WhisperGraph.

IPv6 resolution

WHOIS identity

Registrar
iana:600
Registrant organisation
l'arena des canadiens
Contact emails
pebelzile@canadiens.com

Subdomains

Subdomain
boutique.osheaga.com
play.osheaga.com
store.osheaga.com
www.osheaga.com

Showing 4 of 5. 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

  • austin.ns.cloudflare.com
  • kim.ns.cloudflare.com

MX records

  • osheaga-com.mail.protection.outlook.com
  • mxb-00a3a601.gslb.pphosted.com
  • mxa-00a3a601.gslb.pphosted.com

SPF policy

  • ip: 74.91.88.119/32
  • ip: 64.34.154.128/27
  • ip: 184.107.166.160/29
  • ip: 69.90.10.32/28
  • ip: 74.91.88.96/27
  • include: amazonses.com
  • include: spf.emailsignatures365.com
  • a: osheaga.com
  • mx: osheaga.com
  • include: spf.protection.outlook.com
  • include: servers.mcsv.net
  • ip: 207.35.68.29
  • ip: 207.61.47.194
  • ip: 209.235.143.7
  • ip: 50.100.3.118
  • ip: 52.3.142.185
  • ip: 54.164.133.146
  • ip: 54.39.184.180
  • ip: 54.86.6.47
  • ip: 64.225.152.168
  • ip: 64.225.152.170
  • ip: 64.225.152.171
  • ip: 69.90.179.34

Threat-feed evidence

History

Related pages

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