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
Open
Cached
·
just now
93/100
SECURITY SCORE
Certificate Information
Subject
C=AT, O=PricewaterhouseCoopers IT Services Limited, OU=IFS, CN=remoteworkassistant.pwc.at
Issuer
O=PricewaterhouseCoopers IT Services Limited, CN=PwCIssuing-3A
Valid From
October 30, 2025
Valid Until
October 30, 2027
682 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
80:6A:B2:C3:DF:3D:C0:C0:0B:83:2B:35:0B:AB:D0:41:40:9C:8B:0B:22:19:6C:49:F9:0C:64:9D:A1:39:4B:12
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
Excellent
max-age=31536000; includeSubDomains; preload
Content-Security-Policy
Good
default-src; object-src; style-src; +2 more
default-src 'self' blob:;object-src 'none';style-src 'self' 'unsafe-inline';script-src 'self' 'unsafe-inline';font-src 'self' https://fonts.gstatic.com https://cdn.materialdesignicons.com;
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
- • 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