Skip to main content

Security report for autoketing.org

Other · United States

Medium risk. 6 critical or high findings in SSL/TLS, Security headers and 1 other check.

Security score

52/100

Risk levelMedium

0–100, higher is better. How it is calculated

The domain autoketing.org currently hosts no accessible website content and returns a standard 404 error page. The domain is registered through a privacy protection service based in the US and uses Cloudflare for DNS hosting. There is no visible business information, contact details, or policies on the site, indicating it is either inactive or under development. The lack of content and transparency significantly limits the ability to assess the business or its market position. From a technical perspective, the site uses Cloudflare DNS but lacks any detectable CMS, scripts, or analytics tools. The site is minimal and does not implement security headers or privacy compliance mechanisms. The SSL configuration is basic but present, as the domain uses HTTPS. Mobile optimization and SEO are minimal due to the lack of content. Security posture is weak due to missing security headers and absence of privacy or incident response policies. No vulnerabilities or malicious indicators are detected, but the site’s lack of content and transparency pose risks for trust and credibility. The domain registration is consistent and legitimate, but the privacy protection and minimal content reduce confidence. Overall, the site is non-functional and provides no business or security assurances. Strategic recommendations include publishing clear business and privacy information, implementing security best practices, and improving content quality to build trust and compliance.

Scanned

This is an earlier scan of autoketing.org. View the latest report

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

6 findings rated critical or high. Fix these first.

  1. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

  2. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  3. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

Need hands-on remediation? Email guard@offseq.com

Keep watching autoketing.org

This scan found 22 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
0
Security headers
35
Email security
55
DNS health
80
Network security
100
GDPR outside view
40
Average
52

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The domain autoketing.org appears to be inactive or under development, with no visible business information or services offered. The domain is registered since 2018 with privacy protection, suggesting the owner prefers anonymity or the site is not yet launched. There is no evidence of market positioning, revenue streams, or partnerships. The lack of contact details and policies indicates no active customer engagement or compliance focus. The business intelligence is minimal due to absence of data.

Security posture

The security posture is weak due to lack of security headers, absence of privacy and cookie policies, and no incident response information. The domain uses HTTPS but does not enable DNSSEC, which could improve domain security. No security frameworks or certifications are indicated. The site does not expose sensitive data or show signs of vulnerabilities, but the minimal implementation of security best practices and lack of transparency reduce overall security maturity.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy to improve compliance and user trust.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Enable DNSSEC on the domain to enhance DNS security.
  4. Add clear contact information and incident response channels to improve transparency and readiness.
  5. Develop meaningful website content and improve design and navigation to enhance user experience and credibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
inconsistent

Technology

Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
30/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website is currently inaccessible with a 404 error page.
  2. No business or contact information is available on the site.
  3. No privacy, cookie, or terms of service policies found.
  4. No forms, scripts, or tracking technologies detected.
  5. Domain is registered with privacy protection and uses Cloudflare DNS.
  6. No security headers or advanced security configurations detected.
  7. No analytics or marketing tools detected.
  8. Content quality and website professionalism are very poor due to lack of content.
  9. No suspicious or malicious indicators found but site is effectively non-functional.
Technical notes

Notes

The website currently serves only a 404 error page with minimal HTML content and no detectable scripts or frameworks. The domain uses Cloudflare DNS servers but does not enable DNSSEC. No CMS or hosting platform is identifiable. The site lacks meta tags, SEO optimization, and accessibility features. Performance is moderate due to minimal content but the site is not functional. Mobile optimization is basic given the simple error page. Overall, the technical implementation is minimal and requires significant development to support a functional business website.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Earlier scans of this domain

  1. 66/100Medium33 findingsView report
Reviews of this site

Share your experience with autoketing.org. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review autoketing.org.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.