Skip to content

Hostname

transcontinental.ca

Last fetched

transcontinental.ca resolves to 199.21.218.160, announced in 199.21.216.0/22 by LIBEO-NOCX-1 - Libeo Inc. in CA. transcontinental.ca 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 · transcontinental.caRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.0/10canon.whisper.security/host/transcontinental.ca

Resolution chain

IPv6 resolution

No AAAA record for transcontinental.ca is recorded in WhisperGraph.

Attribution

libeo

ORIGIN_AS

WHOIS identity

Registrar
registrar:easydns technologies inc.
Registrant organisation
transcontinental
Contact emails
legal@transcontinental.ca

Subdomains

Mail and authentication

Nameservers

  • ns1.d-zone.ca
  • ns2.d-zone.ca
  • dns03.transcontinental.ca

MX records

  • transcontinental-ca.mail.protection.outlook.com

SPF policy

  • ip: 67.231.149.106/32
  • ip: 54.173.83.138/32
  • ip: 50.100.15.145/32
  • ip: 52.1.14.157/32
  • ip: 107.23.16.222/32
  • ip: 107.20.210.250/32
  • a: transcontinental.ca
  • mx: transcontinental.ca
  • include: spf.protection.outlook.com
  • include: servers.mcsv.net
  • include: spf.mtasv.net
  • ip: 198.235.60.176
  • ip: 198.235.61.178
  • ip: 198.235.61.227
  • ip: 198.235.61.228
  • ip: 207.107.246.117
  • ip: 207.107.246.118
  • ip: 207.107.246.139
  • ip: 207.107.246.50
  • ip: 208.91.248.100
  • ip: 208.91.248.101
  • ip: 208.91.248.94
  • ip: 208.91.248.95
  • ip: 208.91.248.96
  • ip: 208.91.248.97
  • ip: 208.91.248.98
  • ip: 208.91.248.99
  • ip: 67.22.236.117
  • ip: 67.22.236.118
  • ip: 67.22.236.139
  • ip: 67.231.157.102

Threat-feed evidence

History

Related pages

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