Skip to main content

Security report for aidesignqa.com

AIDQA · Technology · N/a

Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

63/100

Risk levelMedium

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

AIDQA is a technology startup offering a SaaS web application that provides automated design quality assurance for AI-generated user interfaces. The platform targets indie hackers, startup teams, and design engineers who need fast, reliable QA for UI generated by AI tools. The service focuses on detecting layout drift, hierarchy issues, spacing inconsistencies, and accessibility risks, delivering prioritized findings with actionable repair guidance. The website is professionally designed, mobile-optimized, and uses modern web technologies including Next.js and PostHog analytics. Hosting is provided via Vercel with DNS managed by Vercel DNS servers. Security posture is generally good with HTTPS enforced and domain transfer protection enabled, but lacks DNSSEC and security headers. The domain WHOIS data is suspicious due to a future creation date, which may indicate a data error or placeholder registration, slightly reducing trustworthiness. No privacy cookie consent or terms of service pages were found, which impacts privacy compliance. Contact information is limited to a company email and a contact form for early access requests. Overall, the site is well-positioned as a niche SaaS tool in the AI design QA market with a strong technical foundation but could improve transparency and security practices.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
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. 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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';…

  2. GDPR outside view

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

    • 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. 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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching aidesignqa.com

This scan found 25 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
69
Security headers
30
Email security
70
DNS health
55
Network security
100
GDPR outside view
53
Average
63

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

AIDQA operates in the technology sector, focusing on automated QA for AI-generated UI. Its business model is SaaS with a free tier and paid plans. The target market includes solo developers, startup teams, and design systems groups needing fast, automated design checks. The company emphasizes reducing design debt and improving UI consistency and accessibility. The website content and branding are consistent and professional, supporting a small startup profile founded in 2026. There is no evidence of parent or subsidiary companies. The company uses modern analytics and hosting platforms but lacks visible certifications or trust badges. The absence of phone or physical address limits direct contact options. The business appears early stage but with a clear niche and value proposition.

Security posture

The website enforces HTTPS and has domain transfer protection, which are positive security indicators. However, DNSSEC is not enabled, and no security headers such as Content-Security-Policy or X-Frame-Options were detected in the HTML content, which are recommended best practices. There is no public security policy, incident response information, or vulnerability disclosure program visible. The use of PostHog analytics involves moderate user tracking but no explicit privacy controls or cookie consent mechanisms were found, which may raise GDPR compliance concerns. The suspicious WHOIS domain creation date reduces trust in domain legitimacy. Overall, the security posture is moderate but could be improved by adding security headers, enabling DNSSEC, publishing security policies, and implementing privacy compliance mechanisms.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and trust.
  2. Implement and publish a comprehensive privacy policy including cookie consent and GDPR compliance details.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance web security.
  4. Publish a security policy and incident response contact information to improve transparency and trust.
  5. Verify and correct WHOIS domain registration data to remove inconsistencies and improve legitimacy perception.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
AIDQA
Description
AIDQA automatically audits AI-generated interfaces for layout drift, hierarchy issues, spacing inconsistency, and accessibility risk. It provides prioritized findings and repair guidance before shipping.
Key services
Automated design QA for AI-generated interfaces, Layout, hierarchy, consistency, and accessibility checks, Prioritized findings with evidence and repair guidance
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, PostHog analytics, Vercel DNS
Frameworks
Next.js
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status

Analytics and tracking

Services
PostHog
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
PostHog
Marketing tools
PostHog
Transparency
basic

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is fully accessible with rich content and no blocking detected
  2. No explicit privacy or cookie consent mechanisms visible
  3. Contact email is a professional company domain email
  4. No phone numbers or physical addresses found
  5. No terms of service or security policy pages detected
  6. Uses modern web technologies and analytics tools
  7. No visible security headers detected in HTML content
  8. No vulnerability disclosure or security.txt found
  9. Domain WHOIS data is suspicious due to future creation date
Technical notes

Notes

The website is built using Next.js framework with React, hosted on Vercel platform using Vercel DNS. It uses PostHog for analytics, including web vitals, dead click autocapture, surveys, and session recording. The site is mobile-optimized, fast loading, and uses modern font and image preloading techniques. No CMS was detected, indicating a custom or framework-based build. The site lacks some security headers and DNSSEC, which are technical gaps. The domain WHOIS data shows a future creation date, which is likely a data error but should be corrected. Overall, the technical infrastructure is modern and performant but could benefit from enhanced security configurations and privacy compliance features.
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

Reviews of this site

Share your experience with aidesignqa.com. 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 aidesignqa.com.

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.