Skip to main content

Security report for home.blog

Other · United States

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

Security score

62/100

Risk levelMedium

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

Home.blog is a small-scale blog hosted on WordPress.com, focusing on themes related to Appalachia, Artificial General Intelligence (AGI), and Automattic. The site features artwork by Michael Bierut and is designed by Kjell Reigstad. The content is primarily informational and artistic, targeting a general audience interested in these topics. The website leverages WordPress technologies and is hosted by Automattic, ensuring a stable and secure hosting environment. The technical infrastructure is modern, utilizing WordPress core, Jetpack, and Google Fonts, with good mobile optimization and moderate performance. Security posture is solid with HTTPS enabled and no visible vulnerabilities, though security headers and formal policies are lacking. Privacy compliance is minimal, with no visible privacy or cookie policies, and no contact information is provided, which limits business credibility. Overall, the site is safe, professional, and consistent in branding but would benefit from enhanced privacy and security disclosures.

Scanned

NIS2 and GDPR posture

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

    • High

      No DMARC record found

      DMARC provides email authentication and reporting

      What to do: Add DMARC record: "v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com"

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

Keep watching home.blog

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. 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
42
Security headers
30
Email security
65
DNS health
75
Network security
100
GDPR outside view
58
Average
62

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

The website operates as a personal or thematic blog rather than a commercial business, with no explicit business model or revenue streams evident. It targets enthusiasts of art, technology, and regional topics related to Appalachia and AGI. The site references partnerships or related entities such as Pentagram, Automattic, and educational institutions, indicating a network of related interests rather than formal business partnerships. The domain age and registration data are consistent with the site's content and hosting provider. The lack of contact details and formal policies suggests a low level of commercial intent or formal business operations.

Security posture

The website demonstrates a basic to moderate security posture. HTTPS is properly configured with valid SSL certificates, and no sensitive data exposure or vulnerable libraries were detected. However, the absence of security headers such as Content-Security-Policy, X-Frame-Options, and others reduces the overall security hardening. There are no visible incident response or security policies, and no vulnerability disclosure mechanisms are present. The site uses WordPress.com infrastructure, which provides baseline security, but the site owner should consider adding formal policies and security headers to improve resilience and compliance.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy to improve GDPR and privacy compliance.
  2. Add security headers like Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance security posture.
  3. Provide clear contact information and a security incident response policy to improve trust and readiness.
  4. Enable DNSSEC for the domain to strengthen DNS security.
  5. Consider adding a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Artwork by Michael BierutSite by Kjell Reigstad
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Jetpack, Gutenberg, Google Fonts, Twemoji
Frameworks
WordPress
Platforms
WordPress.com
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data
  • No vulnerable libraries detected

Analytics and tracking

Services
WordPress.com Stats
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
wordpress.com pixel, wp.com tracking
Marketing tools
Jetpack, WordPress.com Actionbar
Transparency
basic

Site quality

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

Key observations

  1. Website is a WordPress.com hosted blog focused on artwork and technology topics.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. No contact emails or phone numbers explicitly provided.
  4. No security or incident response policies disclosed.
  5. Site uses HTTPS with valid SSL and modern WordPress technologies.
  6. No WAF or blocking mechanisms detected.
  7. External links mostly point to related organizations and WordPress services.
  8. Content is safe and suitable for general audiences.
  9. Moderate use of tracking and analytics via WordPress.com services.
Technical notes

Notes

The website is built on WordPress CMS hosted on WordPress.com by Automattic, using modern technologies including Jetpack and Gutenberg blocks. The site loads Google Fonts asynchronously and uses Twemoji for emoji support. Performance is moderate with standard WordPress.com optimizations. The site is mobile optimized and accessible at a basic level. SEO is basic with meta tags and Open Graph tags present but no advanced structured data like JSON-LD. No broken elements or errors were detected. The site could benefit from enhanced accessibility features and more comprehensive SEO markup.
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 home.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 home.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.