DNS Gurus

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:

Unknown Certificate Authority - the server's certificate is not trusted

Cached · just now
87/100 SECURITY SCORE

Certificate Information

Subject
C=ES, ST=MD, L=Madrid, O=Base10 Stic, OU=OU, CN=SophosApplianceCertificate_C1A0CBFG642TW84, [email protected]
Issuer
C=ES, ST=MD, L=Madrid, O=Base10 Stic, OU=OU, CN=Sophos_CA_C1A0CBFG642TW84, [email protected]
Valid From
August 01, 2015
Valid Until
December 31, 2036 4004 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F4:1D:42:56:46:64:04:D1:F1:6B:27:05:88:AA:25:50:BA:B1:57:D7:69:8B:D9:64:31:55:F2:5B:4D:7D:04:2C

Security Configuration

TLS Protocols
TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • • TLS 1.3 is not supported (recommended)

HTTP Security Headers

Status
Strict-Transport-Security
Present
max-age=31536000
Content-Security-Policy
Basic
default-src; worker-src; frame-ancestors; +1 more
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • • 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