DNS Gurus
Cached · just now
92/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
GoDaddy logo GoDaddy

Certificate Information

Subject
CN=support.atsiusa.com
Issuer
C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., OU=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
Valid From
October 05, 2025
Valid Until
October 05, 2026 148 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A9:17:21:5A:C6:62:60:5F:D9:10:55:D2:3C:C2:35:16:16:1C:EF:8F:07:01:65:BA:AF:D5:46:3C:95:BD:F1:13
Alternative Names
1 domains

Security Configuration

TLS Protocols
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
Basic
style-src; block-all-mixed-content; object-src; +4 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • • 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

Subject Alternative Names

1 domain
support.atsiusa.com