Skip to content

Hostname

powergate.ca

Last fetched

powergate.ca resolves to 208.74.208.10, announced in 208.74.208.0/21 by RCC-CCTL - Rogers Communications Canada Inc. in CA. powergate.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 · powergate.caRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/powergate.ca

Resolution chain

IPv6 resolution

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

Attribution

rogers canada

ORIGIN_AS

WHOIS identity

Registrar
registrar:csc corporate domains (canada) company
Registrant organisation
rogers communications partnership
Contact emails
domadmin@rci.rogers.com

Subdomains

Subdomain
backup.powergate.ca
cpe.powergate.ca
e911.powergate.ca
filer1.powergate.ca
filer2.powergate.ca
gpon-cpe.powergate.ca
helpdesk.powergate.ca
lsn-gw1.powergate.ca
lsn-gw2.powergate.ca
lsn-gw3.powergate.ca
lsn-gw4.powergate.ca
lsn-gw5.powergate.ca

Showing 12 of 383. View all subdomains →

Mail and authentication

Nameservers

  • ns1.compton.net
  • ns2.compton.net
  • ns3.compton.net
  • ns4.compton.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • prefix1.powergate.ca
  • prefix2.powergate.ca

SPF policy

  • ip: 208.74.208.1/25
  • ip: 2604:4c00:0000:0064::/64
  • mx: powergate.ca
  • include: srs.bis.na.blackberry.com
  • include: gprs.rogers.com
  • include: compton.net
  • include: telus.net

Threat-feed evidence

History

Related pages

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