Skip to main content

Security report for bday.quest

Technology · N/a

Medium risk. 7 critical or high findings in Email security, Security headers and 2 other checks.

Security score

65/100

Risk levelMedium

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

bday.quest is a small, beta-stage online platform focused on creating and sharing virtual birthday cards. The service allows users to create a card, collect personalized birthday wishes via a shared link, and celebrate together by revealing the card on the special day. The website targets a general audience interested in digital greeting solutions and leverages modern web technologies such as Next.js and Clerk.js for authentication and frontend rendering. The platform is positioned as a niche player in the virtual greeting card market with a simple and user-friendly interface. From a technical perspective, the website employs a modern React-based framework (Next.js) and integrates Clerk.js for user authentication. The site shows moderate performance and good mobile optimization but lacks advanced SEO and accessibility features. There is no evidence of a CMS or specific hosting provider from the data provided. The site does not appear to use analytics or advertising technologies, indicating a minimal tracking approach. Security posture is weak due to the absence of visible security headers, lack of privacy and cookie policies, and no contact or incident response information. The domain WHOIS data is privacy protected, which is common for small startups but reduces transparency. No critical vulnerabilities or exposed sensitive data were detected in the HTML content. Overall, the site is safe for general audiences but requires improvements in security and compliance to enhance trustworthiness. The overall risk is moderate with recommendations to implement security best practices, add privacy and cookie policies, and provide clear contact and incident response information to improve compliance and user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 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

7 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

  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 bday.quest

This scan found 23 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
72
Security headers
35
Email security
60
DNS health
75
Network security
100
GDPR outside view
50
Average
65

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

bday.quest operates in the technology sector, specifically in the online greeting card niche. Its business model revolves around providing a free or low-barrier platform for users to create and share virtual birthday cards, potentially monetizing through premium features or partnerships in the future. The platform's competitive advantage lies in its simplicity and social sharing capabilities. The target customers are individuals seeking digital alternatives to traditional birthday cards. The service is in beta, indicating early-stage development and market testing. No partnerships or parent company affiliations are evident. Growth indicators include the number of cards created (156) and wishes collected (345), suggesting initial user engagement. The lack of detailed business information and contact data limits deeper business intelligence insights.

Security posture

The current security maturity level of bday.quest is low. The website lacks essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options, which are critical for mitigating common web attacks. There is no visible privacy policy or cookie consent mechanism, indicating non-compliance with GDPR and other privacy regulations. The absence of contact information for security incidents or abuse reports reduces incident response readiness. No known vulnerabilities or exposed sensitive data were detected, but the lack of security best practices and transparency poses risks. The use of Clerk.js for authentication is a positive security indicator, assuming proper backend implementation. Overall, the site requires significant improvements in security policies, headers, and compliance to reduce risk and build user trust.

Recommendations

  1. Implement comprehensive privacy and cookie policies with clear GDPR compliance statements.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection.
  3. Provide clear contact information including security and abuse reporting channels.
  4. Deploy a vulnerability disclosure policy and publish a security.txt file to encourage responsible reporting.
  5. Enhance SEO and accessibility features to improve user experience and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Create virtual birthday cards
Key services
Create virtual birthday cards, Collect personalized birthday wishes, Share cards via link
Content quality
good
Branding
consistent

Technology

Stack
React, Next.js, Clerk.js
Frameworks
Next.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is a beta service for virtual birthday cards.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails, phone numbers, or physical addresses provided.
  4. Uses modern web technologies including Next.js and Clerk.js for authentication.
  5. No security headers detected in provided data.
  6. No analytics or advertising scripts detected.
  7. Content is safe and family-friendly.
  8. Domain WHOIS data is privacy protected, limiting transparency.
  9. No forms with fields detected in the HTML content provided.
Technical notes

Notes

The website is built using Next.js, a modern React framework, and integrates Clerk.js for user authentication. The frontend is well-structured with responsive design and good mobile optimization. Performance is moderate, with asynchronous loading of scripts and preloading of fonts and styles. However, there is no evidence of a CMS or hosting provider details. SEO is basic with standard meta tags and Open Graph data but lacks structured data like JSON-LD. Accessibility is basic with no explicit ARIA roles or landmarks detected. No analytics or advertising scripts were found, indicating minimal tracking. The site would benefit from improved accessibility, SEO enhancements, and security header implementation to reduce technical risks.
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 bday.quest. 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 bday.quest.

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.