DNS Gurus
Cached · just now
86/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 27
Gravatar logo Gravatar Shields.io logo Shields.io Algolia logo Algolia Atlassian logo Atlassian AWS Certificate Manager logo AWS Certificate Manager Amazon S3 logo Amazon S3 Contentful logo Contentful Contentsquare logo Contentsquare Active incidents Figma logo Figma Google Analytics logo Google Analytics Google Conversion Tracking logo Google Conversion Tracking Google DoubleClick logo Google DoubleClick Google Fonts logo Google Fonts Google Search logo Google Search Google Static File Front End logo Google Static File Front End Google Tag Manager logo Google Tag Manager jsDelivr logo jsDelivr LaunchDarkly logo LaunchDarkly Active incidents LinkedIn logo LinkedIn OneTrust logo OneTrust Qualtrics logo Qualtrics Segment logo Segment Sentry logo Sentry Vimeo logo Vimeo WordPress logo WordPress YouTube logo YouTube Google Cloud logo Google Cloud

Certificate Information

Subject
CN=*.frontend.public.atl-paas.net
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
July 24, 2026
Valid Until
February 06, 2027 193 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F3:EC:D2:FE:A2:66:25:2A:0D:04:A1:E3:4B:5A:C2:EA:8D:B4:05:16:0A:66:70:46:8E:86:4B:71:67:ED:9C:10
Alternative Names
53 domains

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=63072000; preload
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Shields.io logo
Good
default-src; base-uri; font-src; +9 more Analyze
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
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • 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