Scan history
Security checks — sorted by severity
MX Records & Mail Provider
Strengths: Mail handled by Microsoft 365; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
Strengths: Mail handled by Microsoft 365; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.
DNS CAA Records
No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.
No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.
DNS Configuration
Strengths: 6 nameservers configured (a22-66.akam.net, a10-64.akam.net, a8-64.akam.net, a7-67.akam.net...); SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s). Issues: All nameservers are from a single provider (akam.net) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Strengths: 6 nameservers configured (a22-66.akam.net, a10-64.akam.net, a8-64.akam.net, a7-67.akam.net...); SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s). Issues: All nameservers are from a single provider (akam.net) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy. Quality issues: CSP: 'unsafe-inline' in script directives — negates XSS protection; CSP: 'unsafe-eval' allows eval() — weakens XSS protection.
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy. Quality issues: CSP: 'unsafe-inline' in script directives — negates XSS protection; CSP: 'unsafe-eval' allows eval() — weakens XSS protection.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: selector2, s1, s2, k1). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright.
Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: selector2, s1, s2, k1). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright.
security.txt (RFC 9116)
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Known Breaches
No known breaches found in public disclosure databases.
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=63072000s (730 days) with includeSubDomains and preload. Meets best-practice configuration.
HSTS enabled: max-age=63072000s (730 days) with includeSubDomains and preload. Meets best-practice configuration.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
No cookies set on the homepage response. No cookie security flags to evaluate.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Certificate Hygiene
Strengths: Certificate valid, 214 days remaining; Issued by Sectigo Limited.
Strengths: Certificate valid, 214 days remaining; Issued by Sectigo Limited.
Recommended actions
1+ items
Steps to improve manulife.ca's security grade, ranked by impact.
1
Strengthen email authentication configuration
DMARC / Email Security
Email authentication is partially configured for manulife.ca but has gaps. Actions needed: . Until DMARC enforcement is active, spoofed emails may still reach recipients.
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Verify with: nslookup -type=txt _dmarc.manulife.ca
See all 2 remaining recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
AI Summary
What this means
manulife.ca scored 85/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: TLS Configuration, TLS Protocol Support, Known Breaches all passed.
3 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How manulife.ca compares
Grade distribution across 2685 companies we've scanned. manulife.ca scores better than 78% of them.
88
A+
28
A
196
A-
202
B+
76
B
376
B-
138
C+
117
C
347
C-
123
D+
96
D
266
D-
632
F
manulife.ca — Grade B (85/100)
2685 companies scanned
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: selector2, s1, s2, k1). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright.
SPF Record
Present
v=spf1 include:manulife.ca._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=63072000s (730 days) with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 214 days remaining; Issued by Sectigo Limited.
DNSSEC
Not enabled
Strengths: 6 nameservers configured (a22-66.akam.net, a10-64.akam.net, a8-64.akam.net, a7-67.akam.net...); SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s). Issues: All nameservers are from a single provider (akam.net) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Similar companies
Other domains with comparable security profiles.
