Overview
Findings
Actions
Details
Related
A
95 / 100

fortisinc.com

Security report · Scanned May 12, 2026

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

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

Positive signals: DNS Configuration, TLS Configuration, DMARC / Email Security all passed.

1 action item 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 fortisinc.com compares

Grade distribution across 2655 companies we've scanned. fortisinc.com scores better than 96% of them.

96th percentile
0 Percentile rank 100
88
A+
27
A
191
A-
198
B+
75
B
371
B-
137
C+
117
C
342
C-
122
D+
95
D
261
D-
631
F
fortisinc.com — Grade A (95/100) 2655 companies scanned
Security checks

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

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
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
DNS CAA Records
No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.
Needs work
Security Headers
3/5 security headers present. Missing: X-Frame-Options, Permissions-Policy.
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
DNS Configuration
Strengths: 5 nameservers configured (ns0.dnsmadeeasy.com., ns1.dnsmadeeasy.com., ns2.dnsmadeeasy.com., ns4.dnsmadeeasy.com.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Healthy
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present; DKIM configured (selectors: selector1, selector2).
Healthy
Known Breaches
No known breaches found in public disclosure databases.
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=63072000s (730 days) with includeSubDomains and preload. Meets best-practice configuration.
Healthy
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
Healthy
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.
Healthy
Certificate Hygiene
Strengths: Certificate valid, 98 days remaining; Issued by DigiCert Inc.
Healthy
Recommended actions
1 item

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

1
Add optional security headers (X-Frame-Options, Permissions-Policy)
Impact: < 1 Hour
LOW
fortisinc.com has most security headers configured. Missing: X-Frame-Options, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: X-Frame-Options: SAMEORIGIN (use DENY only if you never embed your pages in iframes)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://fortisinc.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
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=reject
Strengths: DMARC policy set to reject (strongest); SPF record present; DKIM configured (selectors: selector1, selector2).
SPF Record
Present
v=spf1 redirect=fortisinc.com.hosted.spf-report.com
Security Headers
3/5 present
Missing: X-Frame-Options, 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, 98 days remaining; Issued by DigiCert Inc.
DNSSEC
Enabled
Strengths: 5 nameservers configured (ns0.dnsmadeeasy.com., ns1.dnsmadeeasy.com., ns2.dnsmadeeasy.com., ns4.dnsmadeeasy.com.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.