Overview
Findings
Actions
Details
Related
A-
92 / 100

fortisalberta.com

Security report · Scanned February 26, 2026

Checks
14
Passed
7
Warnings
7
Critical
0
AI-Generated Summary
What this means

fortisalberta.com scored 92/100, demonstrating a strong security posture. Minor improvements are noted below.

Positive signals: TLS Configuration, HSTS Header, Security Headers all passed.

2 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 fortisalberta.com compares

Grade distribution across 2378 companies we've scanned. fortisalberta.com scores better than 92% of them.

92th percentile
0 Percentile rank 100
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
fortisalberta.com — Grade A- (92/100) 2378 companies scanned
Security checks

Each check inspects a different part of fortisalberta.com's public security setup. Green means healthy, yellow needs attention, red is a problem.

MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
Needs work
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.
Needs work
DNS CAA Records
Strengths: CAA records configured (3 record(s)); Authorized CAs: entrust.net, godaddy.com, digicert.com. Issues: No iodef record — CA violations won't be reported to the domain owner.
Needs work
DNS Configuration
Strengths: 3 nameservers configured (dns3.easydns.org., dns2.easydns.net., dns1.easydns.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Needs work
Cookie Security
Strengths: 4 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag. Issues: 2/4 cookie(s) missing SameSite attribute (ARRAffinity, ARRAffinity).
Needs work
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.
Needs work
Certificate Hygiene
Strengths: Certificate valid, 373 days remaining; Issued by GoDaddy.com, Inc.; 631 certificates logged in CT. Issues: Certificates issued by 9 different CAs (threshold: 8 for 631 logged certs) — possible misconfiguration or shadow IT.
Needs work
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
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.
Healthy
HSTS Header
HSTS enabled: max-age=31536000s (365 days). includeSubDomains present. Missing preload directive.
Healthy
Security Headers
All 5 recommended security headers present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
Healthy
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: selector1, selector2, smtpapi).
Healthy
Known Breaches
No known breaches found in public disclosure databases.
Healthy
CVE Exposure
Detected technologies: Microsoft-IIS/10.0, ASP.NET. No high or critical CVEs found for detected versions.
Healthy
Recommended actions
2 items

Steps to improve fortisalberta.com's security grade, ranked by impact.

1
Enable DNSSEC on your domain
Impact: 1–3 Days (Depends On Registrar)
MEDIUM
Without DNSSEC, DNS responses for fortisalberta.com can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .com TLD
4
Verify: dig +dnssec fortisalberta.com
2
Review certificate configuration
Impact: 1–2 Hours
LOW
Certificate issues found for fortisalberta.com: . These are operational hygiene items, not immediate security risks.
How to fix this
1
Consolidate certificate issuance to 1–2 trusted CAs
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; SPF record present with soft-fail (~all); DKIM configured (selectors: selector1, selector2, smtpapi).
SPF Record
Present
v=spf1 include:fortisalberta.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~
Security Headers
5/5 present
All headers configured.
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days). includeSubDomains present. Missing preload directive.
SSL Certificate
Issues
Strengths: Certificate valid, 373 days remaining; Issued by GoDaddy.com, Inc.; 631 certificates logged in CT. Issues: Certificates issued by 9 different CAs (threshold: 8 for 631 logged certs) — possible misconfiguration or shadow IT.
DNSSEC
Not enabled
Strengths: 3 nameservers configured (dns3.easydns.org., dns2.easydns.net., dns1.easydns.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.