Skip to main content

Security report for dotart.blog

Privacy service provided by Withheld for Privacy ehf · Media · Iceland

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

66/100

Risk levelMedium

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

dotart.blog is a small, community-focused blogging platform serving as a sister site to mastodon.art, targeting users interested in longer form creative writing such as poetry and stories. It leverages the open-source WriteFreely platform to provide decentralized blogging capabilities with markdown support and integration with the mastodon.art social network. The website is modest in scale but offers a niche service for its target audience. Technically, the site is built on WriteFreely CMS, hosted via Namecheap, and uses basic web technologies including CSS and JavaScript. Performance is moderate with a page load time of approximately 4 seconds and minimal resources. The site lacks HTTPS, which is a significant technical and security shortcoming. SEO and accessibility are basic but functional. From a security perspective, the absence of a valid SSL certificate and HTTPS is a critical vulnerability, exposing users to potential interception risks. No security headers or advanced protections are implemented, and no incident response or vulnerability disclosure policies are present. Privacy compliance is minimal, with a basic privacy policy but no cookie consent mechanisms or GDPR compliance indicators. Overall, the site is functional and serves its community purpose but requires urgent improvements in security posture, including enabling HTTPS, adding security headers, and enhancing privacy compliance to build trust and protect users effectively.

Scanned

This is an earlier scan of dotart.blog. 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. 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 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

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

Keep watching dotart.blog

This scan found 21 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. 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
100
Security headers
15
Email security
70
DNS health
70
Network security
100
GDPR outside view
40
Average
66

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention dotart.blog, from OffSeq Breach.

No leaked records found

Breach holds no records for dotart.blog right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

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

Business context

Business profile

The platform operates in the media sector as a niche blogging community extension linked to mastodon.art. Its business model appears community-driven and invitation-based, focusing on creative writers within the fediverse ecosystem. The site benefits from association with mastodon.art, providing a competitive advantage in a specialized market. Growth potential depends on expanding user adoption and improving platform features. The use of privacy protection in domain registration aligns with community privacy values but limits transparency. No direct revenue streams or monetization strategies are evident from the data. Partnerships are primarily with open-source projects and the mastodon.art community. The platform's small size and focused audience suggest a boutique operation with limited commercial ambitions but strong community engagement.

Security posture

The current security posture is weak due to the lack of HTTPS and SSL certificate, which is a critical issue. No security headers or advanced configurations such as HSTS or CSP are implemented. The site does not use DNSSEC or CAA records, though no DNS vulnerabilities were detected. No vulnerability disclosure or incident response policies are published, indicating low maturity in security governance. Privacy compliance is minimal, with no cookie consent or GDPR adherence visible. The absence of contact information for security incidents further reduces readiness. Overall, the site is vulnerable to common web threats and requires immediate remediation to protect user data and trust.

Recommendations

  1. Obtain and install a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security with preload.
  3. Add a cookie policy and consent mechanism to comply with privacy regulations.
  4. Publish a vulnerability disclosure policy and incident response contact information to improve security transparency.
  5. Enhance privacy policy to explicitly address GDPR compliance and data protection practices.
Technical notes

Notes

The website uses the WriteFreely CMS platform, which is suitable for decentralized blogging and supports markdown and CSS theming. Hosting is provided via Namecheap with DNS managed by registrar-servers.com. The site has moderate performance with a 4-second load time and minimal resource usage. No modern TLS protocols or cipher suites are enabled due to lack of SSL. The site uses basic JavaScript for fonts and menu functionality. SEO metadata is present but minimal. Accessibility and mobile optimization are basic but functional. Technical debt is low but the lack of HTTPS is a major risk. Modernization opportunities include enabling HTTPS, improving security headers, and adding analytics or marketing tools if desired.
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. 63/100Medium35 findingsView report
  2. 63/100Medium35 findingsView report
Reviews of this site

Share your experience with dotart.blog. 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 dotart.blog.

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.