Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
newfoundlandpower.com scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: MX Records & Mail Provider, DMARC / Email Security, 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 newfoundlandpower.com compares
Grade distribution across 2655 companies we've scanned. newfoundlandpower.com scores better than 72% of them.
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
newfoundlandpower.com — Grade B- (82/100)
2655 companies scanned
Security checks
Each check inspects a different part of newfoundlandpower.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.
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.
DNS Configuration
Strengths: 2 nameservers configured (ns2.d-zone.ca., ns1.d-zone.ca.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
TLS Protocol Support
Strengths: TLS 1.2 supported; TLS 1.2 supported (consider enabling TLS 1.3). Protocol support: TLS 1.3: No, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy.
Cookie Security
Strengths: 2 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag. Issues: 1/2 cookie(s) missing SameSite attribute (cookiesession1).
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.
MX Records & Mail Provider
Strengths: Mail handled by mx2.hc464-44.ca.iphmx.com; 2 MX record(s) configured; Multiple MX records provide redundancy; All MX records share the same priority (10) — round-robin load balancing (no primary/backup distinction).
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: s1, s2, dkim).
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31536000s (365 days). includeSubDomains present. Missing preload directive.
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.
Certificate Hygiene
Strengths: Certificate valid, 67 days remaining; Issued by Entrust Limited; 469 certificates logged in CT; Certificates from 8 CAs: "Entrust, "VeriSign, "cPanel.
Recommended actions
1 item
Steps to improve newfoundlandpower.com's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for newfoundlandpower.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 newfoundlandpower.com
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.
2
3
At a glance
Key data points from the scan.
TLS Version
TLSv1.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: s1, s2, dkim).
SPF Record
Present
v=spf1 ip4:198.51.255.0/24 ip4:216.71.131.18 ip4:216.71.133.248 include:_spf.psm.knowbe4.com include
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days). includeSubDomains present. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 67 days remaining; Issued by Entrust Limited; 469 certificates logged in CT; Certificates from 8 CAs: "Entrust, "VeriSign, "cPanel.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (ns2.d-zone.ca., ns1.d-zone.ca.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.