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
96/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=Florida, L=Tampa, O=PricewaterhouseCoopers LLP, OU=Substance Tracker, CN=dev.economicsubtance.trackingsuite.pwc.com, [email protected]
Issuer
O=PricewaterhouseCoopers IT Services Limited, CN=PwCIssuing-3A
Valid From
November 12, 2024
Valid Until
November 12, 2026
326 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
55:30:ED:02:9C:DC:06:31:E6:1D:7D:D2:83:93:CD:09:86:38:CA:87:C6:04:05:97:FD:03:7F:6C:EC:0A:96:9C
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=63072000; includeSubDomains; preload
Content-Security-Policy
Strong
base-uri; child-src; connect-src; +12 more
base-uri 'none';child-src 'self' *.pwc.com *.pwcinternal.com;connect-src 'self' *.pwc.com *.pwcinternal.com dc.services.visualstudio.com *.azurewebsites.net;default-src 'self';font-src 'self' cdn.jsdelivr.net;form-action 'self';frame-ancestors 'self';frame-src 'self' *.pwc.com *.pwcinternal.com;img-src 'self' data:;manifest-src 'self';media-src 'self';object-src 'none';script-src 'self';style-src 'self' 'sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=';worker-src 'self';
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
clipboard-read=(),clipboard-write=(),gamepad=(),accelerometer=(),autoplay=(),camera=(),cross-origin-isolated=(),display-capture=(),encrypted-media=(),fullscreen=(),geolocation=(),gyroscope=(),magnetometer=(),microphone=(),midi=(),payment=(),picture-in-picture=(),publickey-credentials-get=(),screen-wake-lock=(),sync-xhr=(),usb=(),xr-spatial-tracking=()
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