SSL Verification Bypassed

The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.

Reason:

Hostname Mismatch - certificate is issued for cpanel.procomnovotic.com, cpcalendars.procomnovotic.com, cpcontacts.procomnovotic.com, mail.procomnovotic.com, mail.serviceprocom.ca, mail.servicesprocom.ca, procomnovotic.com, serviceprocom.ca, servicesprocom.ca, not for ns2.procomdns.com

91/100 SECURITY SCORE

Certificate Information

Subject
CN=cpcontacts.procomnovotic.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
January 08, 2026
Valid Until
April 08, 2026 84 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
0B:7D:C6:C5:E7:5F:A2:21:CA:0E:1F:22:47:6F:74:03:16:93:1A:89:4D:1E:D2:FE:66:F0:93:37:E4:21:37:70
Alternative Names

Security Configuration

TLS Protocols
TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)

HTTP Security Headers

Status
Strict-Transport-Security
Present
max-age=2592000; includeSubDomains; preload
Content-Security-Policy
Good
default-src; script-src; style-src; +7 more
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
no-referrer, strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Strengthen CSP by removing 'unsafe-eval'
  • Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records
Not Configured (Any CA can issue certificates)
CAA Issues
  • No CAA records configured - any CA can issue certificates
Recommendations
  • Implement CAA records to restrict which CAs can issue certificates for your domain
  • This adds an extra layer of security against unauthorized certificate issuance
  • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
  • Consider adding 'iodef' record to receive security incident reports