Skip to main content

Security report for typo.domains

Technology · N/a

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

64/100

Risk levelMedium

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

The website typo.domains operates as a domain typo finder service, targeting domain owners and brand protectors by offering discovery of valuable typo domain variations that could generate significant revenue. The business model focuses on domain typo protection and investment insights, positioning itself within the technology sector. The site presents a professional and consistent brand image with good content quality and clear navigation, although it lacks detailed business information and contact data. Technically, the site is built using modern web technologies including React and Next.js, with integration of Google Adsense for advertising and Simple Analytics for minimal user tracking. The site is mobile optimized and SEO friendly, but accessibility features are basic. Performance is moderate, and HTTPS is properly implemented, ensuring secure connections. From a security perspective, the site has a good SSL configuration but lacks important security headers and does not provide privacy or cookie policies, which impacts compliance and trust. No forms or user input fields were detected, reducing attack surface, but the absence of incident response or vulnerability disclosure information limits transparency. WHOIS data is unavailable due to unsupported TLD or privacy protection, which is common in this domain niche but reduces registration transparency. Overall, the site is functional and professional but would benefit from enhanced privacy compliance, security headers, and contact transparency to improve trust and security posture. The risk level is moderate with no critical vulnerabilities detected.

Scanned

NIS2 and GDPR posture

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

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

    • 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

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

Keep watching typo.domains

This scan found 24 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. See sample alerts.

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
30
Email security
70
DNS health
75
Network security
100
GDPR outside view
35
Average
64

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

Typo.domains operates in the niche market of domain typo discovery and brand protection, targeting domain owners and investors interested in typosquatting prevention and domain monetization. The business model likely generates revenue through domain sales, protection services, or advertising. The site uses Google Adsense for monetization and Simple Analytics for tracking minimal user data. The lack of detailed company information, contact details, or certifications suggests a small-scale operation. The market positioning appears focused on domain investors and brand managers seeking to protect or capitalize on typo domains. No partnerships or subsidiaries were identified. Growth potential depends on expanding service offerings and improving trust signals.

Security posture

The website demonstrates a basic security posture with HTTPS enabled, ensuring encrypted communications. However, it lacks critical security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options, which are recommended to mitigate common web attacks. No forms or inputs reduce risk of injection attacks. The absence of privacy and cookie policies indicates compliance gaps, particularly with GDPR. No incident response or vulnerability disclosure mechanisms are present, limiting transparency and preparedness. WHOIS privacy protection is used, which is typical but reduces registration transparency. Overall, the security maturity is moderate with room for improvement in headers, policies, and incident readiness.

Recommendations

  1. Implement essential security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web vulnerabilities.
  2. Publish comprehensive privacy and cookie policies to improve GDPR compliance and user trust.
  3. Add clear contact information and a security incident response policy or page to increase transparency and preparedness.
  4. Consider establishing a vulnerability disclosure program or security.txt file to encourage responsible reporting of security issues.
  5. Enhance accessibility features to improve usability for all users and meet compliance standards.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Discover valuable typo variations of your domain name that could be worth $200k+ in revenue. Protect your brand and capture lost traffic.
Key services
finding valuable typo domain variations, brand protection, domain investment insights
Content quality
good
Branding
consistent

Technology

Stack
React, Next.js, Google Adsense, Simple Analytics
Frameworks
Next.js, React
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled

Analytics and tracking

Services
Simple Analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Ad networks
Google Adsense
Tracking pixels
Simple Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is accessible and not blocked by WAF or security mechanisms.
  2. WHOIS data is unavailable due to unsupported TLD or privacy protection.
  3. No contact information or privacy/cookie policies found on the site.
  4. Site uses modern web technologies and has good SEO metadata.
  5. Advertising is present via Google Adsense and minimal tracking via Simple Analytics.
  6. No security headers detected; HTTPS is enabled.
  7. No forms or user input fields detected in the HTML content.
  8. No social media links or company contact emails found.
  9. Content is focused on domain typo discovery and brand protection.
Technical notes

Notes

The website is built on a modern React and Next.js stack, leveraging server-side rendering and client-side hydration for performance and SEO benefits. It uses Google Adsense for monetization and Simple Analytics for privacy-focused tracking. The site loads multiple JavaScript chunks asynchronously, indicating modular code splitting. Preloading of fonts and images is implemented for performance optimization. The site is mobile responsive with a clean, consistent design. However, no CMS or hosting provider information is discernible from the HTML. Performance is moderate, with potential improvements in accessibility and security headers. The lack of forms reduces complexity and attack surface.
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 typo.domains. 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 typo.domains.

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.