hpl.ca security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

49risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

5Medium

7Low

2Info

Collected 7 hours ago3.5sfrom cache

Certificate Transparency34
DNS resolution23
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs52
Registration
DNS posture2
Email authentication2
Certificate
Security headers2
Archived URLs
Analysis14

noteFound 34 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.
note3 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 173.209.49.172:22
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 172.104.219.95:22
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://hpl.ca/
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://hpl.ca/
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: hpl.ca
173.209.49.172 (preview.hpl.ca) reports exim 4.99.5, openssh 9.6p1. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 173.209.49.172
172.104.219.95 (learn.hpl.ca) reports openssh 7.4p1. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 172.104.219.95
vpn.hpl.ca appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: vpn.hpl.ca
preview.hpl.ca appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: preview.hpl.ca
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://hpl.ca/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: hpl.ca
Not urgent, but worth confirming auto-renew is on and the card on file is current.
What to do
Check auto-renew.
asset: hpl.ca
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: hpl.ca
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: hpl.ca

final https://hpl.ca/status 200time 761msstack cloudflare · Drupal 7 (http://drupal.org)

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✓Clickjacking protection
ALLOW-FROM https://hplca.sharepoint.com
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 1 server
hpl-ca.mail.protection.outlook.com
✓SPFends in -all
v=spf1 include:spf.protection.outlook.com ip4:23.185.0.4 ip4:64.191.37.114 ip4:107.6.27.111 ip4:205.201.129.72 ip4:172.105.7.104 include:spf.mandrillapp.com include:mailgun.org -all
!DMARCp=none
v=DMARC1; p=none;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
dns.internic.ca dns2.internic.ca

✓Registered with Internic.ca Inc.25.9 years old
hpl.ca
!Registration expiry49 days
2026-10-27
✓Transfer lock
client transfer prohibited, client update prohibited
✓2 nameservers at registry
dns.internic.ca dns2.internic.ca

Address	Ports	Edge	Network
173.209.49.172 preview.hpl.ca +13	225380110443465993995+7	direct	—
172.66.0.145 help.hpl.ca +3	80443205220532082208320862087+5	Cloudflare~	—
162.159.140.147 help.hpl.ca +3	80443205220532082208320862087+5	Cloudflare~	—
172.104.219.95 learn.hpl.ca +2	2280443	direct	—
23.185.0.4 hpl.ca +16	80443	Fastly~	—
64.191.37.114 vpn.hpl.ca +1	80443	direct	—
3.33.156.228 events.hpl.ca +2	80443	direct	—
15.197.154.66 events.hpl.ca +3	80443	direct	—
64.191.37.120 print.hpl.ca	none known	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

hpl.ca security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames