Overview
Findings
Actions
Details
Related
C-
70 / 100

itc-holdings.com

Security report · Scanned May 12, 2026

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

itc-holdings.com scored 70/100, meeting baseline requirements but with 7 findings that require attention. The vendor can proceed with a remediation timeline agreement.

Critical gaps in: Cookie Security, CVE Exposure. Positive signals: TLS Configuration, TLS Protocol Support, Known Breaches all passed.

4 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 itc-holdings.com compares

Grade distribution across 2655 companies we've scanned. itc-holdings.com scores better than 42% of them.

42th 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
itc-holdings.com — Grade C- (70/100) 2655 companies scanned
Security checks

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

Cookie Security
Strengths: 2 cookie(s) analyzed. Issues: 1/2 cookie(s) missing Secure flag (AWSALB); 2/2 cookie(s) missing HttpOnly flag (AWSALB, AWSALBCORS); 1/2 cookie(s) missing SameSite attribute (AWSALB).
Problem
CVE Exposure
Detected technologies: Apache/2.4.66. 1 critical-severity CVE(s) found (CVSS >= 9.0): CVE-2026-28780. Immediate patching recommended.
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 Configuration
Strengths: 2 nameservers configured (ns43.worldnic.com., ns44.worldnic.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
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: Referrer-Policy, Permissions-Policy.
Needs work
DMARC / Email Security
Strengths: SPF record present with hard-fail (-all); DKIM configured (selectors: cm). Issues: No DMARC record found — email spoofing is not prevented.
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
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-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
Known Breaches
No known breaches found in public disclosure databases.
Healthy
HSTS Header
HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.
Healthy
Certificate Hygiene
Strengths: Certificate valid, 199 days remaining; Issued by Amazon.
Healthy
Recommended actions
1 item

Steps to improve itc-holdings.com's security grade, ranked by impact.

1
Strengthen email authentication configuration
Impact: 2–4 Hours
HIGH
Email authentication is partially configured for itc-holdings.com but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.itc-holdings.com
2
 
 
●●●
3
 
 
●●●
4
 
 
●●●
At a glance

Key data points from the scan.

TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
Not configured
Strengths: SPF record present with hard-fail (-all); DKIM configured (selectors: cm). Issues: No DMARC record found — email spoofing is not prevented.
SPF Record
Present
v=spf1 include:spf.protection.outlook.com -all
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 199 days remaining; Issued by Amazon.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (ns43.worldnic.com., ns44.worldnic.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.