Skip to main content

Security report for sanity.studio

Other · N/a

Partial score · DNS & email only

65/100

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

The website sanity.studio is currently inaccessible, returning a 400 Bad Request error indicating an invalid host usage. This suggests the site requires a specific subdomain format to access content, which was not provided in the request. Due to this, no meaningful website content, metadata, or business information could be extracted or analyzed. The WHOIS data for the domain is unavailable due to the .studio TLD not being supported by the WHOIS service used, resulting in no registrar, creation, expiry, or registrant details. This limits the ability to verify domain legitimacy or business credibility. From a technical perspective, the lack of accessible content and metadata prevents assessment of the technology stack, security headers, or compliance policies. The absence of HTTPS or security headers in the provided data suggests a minimal security posture, though this may be due to the incomplete data. No contact information, privacy policies, or terms of service were found, indicating poor privacy compliance and business transparency. Security posture is weak due to the lack of accessible content and security configurations. The domain's legitimacy is uncertain given the missing WHOIS data and inaccessible website. Overall, the site appears to be either misconfigured or restricted, preventing a full security and compliance evaluation. This poses a risk for users attempting to access the site and limits trust. Strategic recommendations include correcting the domain/subdomain configuration to allow proper access, implementing HTTPS and security headers, publishing privacy and cookie policies, and providing clear contact and incident response information. These steps will improve trust, compliance, and security posture significantly.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
Checks completed
6of 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. 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

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

  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 sanity.studio

This scan found 19 issues across 5 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
Email security
40
DNS health
75
Network security
100
GDPR outside view
40
Average
65

Not counted

  • Security headers: did not complete in this scan.
  • 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

Due to the lack of accessible website content and metadata, no detailed business intelligence could be derived. The domain sanity.studio likely relates to the company Sanity, known for content platform services, but this cannot be confirmed from the data provided. No information on market positioning, business model, revenue streams, or partnerships was found. The absence of contact details and policies further limits business credibility assessment. Without accessible content, it is not possible to analyze target customer segments or growth indicators.

Security posture

The security posture of the domain sanity.studio is currently poor based on the available data. The website is inaccessible, returning a 400 Bad Request error, which may indicate misconfiguration or restrictive access controls. No HTTPS or security headers were detected in the provided content, suggesting minimal security hardening. The absence of privacy policies, cookie consent mechanisms, and contact information indicates compliance gaps with GDPR and other regulations. No incident response or vulnerability disclosure information was found. Overall, the site lacks visible security best practices and transparency, increasing risk for users and stakeholders.

Recommendations

  1. Correct domain and subdomain configuration to ensure website content is accessible to users.
  2. Implement HTTPS with a valid SSL certificate to secure communications.
  3. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Publish comprehensive privacy and cookie policies to comply with GDPR and inform users.
  5. Provide clear contact information including security incident response and abuse contacts to improve trust and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website returns a 400 Bad Request with message 'Invalid host - use <hostname>.sanity.studio' indicating content is blocked or inaccessible. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Performance
slow
Mobile
poor
Accessibility
poor
SEO
poor

Security

Observed score
10/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 content is inaccessible, returning a 400 Bad Request error.
  2. No metadata, scripts, or external links detected in the provided HTML.
  3. No contact information, policies, or business data found.
  4. WHOIS data is unavailable due to unsupported TLD and raw WHOIS output indicates no public data.
  5. No security headers or HTTPS information available from provided data.
  6. Site likely uses a hostname subdomain structure as indicated by error message.
  7. Analysis limited by lack of accessible content and WHOIS data.
Technical notes

Notes

The technical analysis is limited due to the lack of accessible website content. The HTML response indicates a 400 Bad Request error with a message about invalid host usage, suggesting the site requires a specific subdomain format. No metadata, scripts, or external links were found in the provided HTML snippet. No CMS, frameworks, or hosting provider information could be identified. The absence of security headers and HTTPS information points to a minimal technical implementation or incomplete data capture. Performance, mobile optimization, accessibility, and SEO cannot be assessed. The site likely needs configuration adjustments to enable proper access and allow a full technical evaluation.
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 sanity.studio. 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 sanity.studio.

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.