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:

Hostname Mismatch - certificate is issued for www.pb.com, aws-pbstage.pb.com, aws-pbstage.pitneybowes.ca, aws-pbstage.pitneybowes.com, cdn.pbui.us, cl.pb.com, clienthub.pitneybowes.com, de.pbcomcloud.pb.com, en-ca.pbcomcloud.pb.com, not for san.pb.com.edgekey.net

Cached · just now
64/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 2
DigiCert logo DigiCert GeoTrust logo GeoTrust

Certificate Information

Subject
C=US, ST=Connecticut, L=Stamford, O=Pitney Bowes Inc, CN=www.pb.com
Issuer
C=US, O=DigiCert Inc, OU=www.digicert.com, CN=GeoTrust TLS RSA CA G1
Valid From
May 19, 2025
Valid Until
May 18, 2026 11 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D5:A6:E8:E5:45:A9:80:6E:50:24:CB:2D:E2:7C:0F:2A:89:AF:75:55:0C:43:9E:0F:C6:C9:F4:AC:49:A1:A9:F3
Alternative Names
62 domains

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
Missing
Not configured
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • Add X-Content-Type-Options: nosniff
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • • 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