James Greenhalgh on digital strategy, marine conservation, and adventures. · Other · N/a
Medium risk. 8 critical or high findings in DNS health, GDPR outside view and 1 other check.
JamesGreenBlue.com is a personal blog operated by James Greenhalgh focusing on digital strategy, marine conservation, and personal adventures. The site features a collection of blog posts dating from 2020 through 2025, reflecting a niche content approach aimed at environmentally conscious and technology-interested audiences. The business model is primarily content-driven with no evident commercial transactions or services offered. The website is small in scale and founded in 2022, consistent with the domain registration data. Technically, the website is built using the Hugo static site generator, hosted behind Cloudflare DNS services, and leverages Google Fonts for typography. The site is performant, mobile-optimized, and accessible with good SEO practices. No CMS beyond Hugo is detected, and no analytics or tracking scripts are present, indicating a privacy-conscious approach. From a security perspective, the site enforces HTTPS and has domain-level protections such as clientDeleteProhibited and clientTransferProhibited statuses. However, DNSSEC is not enabled, and no security headers are detected in the provided data. There is no published privacy policy, cookie policy, or terms of service, which presents compliance gaps especially regarding GDPR. No contact information or incident response channels are provided, limiting transparency and user trust. Overall, the website is safe, professional, and trustworthy as a personal blog but would benefit from enhanced privacy compliance, security header implementation, and clearer contact information to improve user trust and regulatory adherence.
Scanned
NIS2 Art. 21(2)
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.
8 findings rated critical or high. Fix these first.
DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.
SPF record has permissive policy allowing any server to send email
What to do: Use -all or ~all qualifier for better email security
These are the privacy signals visitors and data protection authorities look for under GDPR.
GDPR requires a clear and accessible privacy policy
What to do: Add a comprehensive privacy policy page and link to it prominently
GDPR requires clear information about cookie usage
What to do: Add a dedicated cookie policy explaining cookie usage and purposes
GDPR requires explicit consent for non-essential cookies
What to do: Implement a cookie consent banner that appears on first visit
Detected services: Google APIs
What to do: Document all third-party data sharing in your privacy policy
Need hands-on remediation? Email guard@offseq.com
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.
€25per month
Email alerts on material changes and an exportable JSON history of every change.
Billed monthly to your card. Cancel anytime. See sample alerts.
€39.90one-time
Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.
Each check with its score, findings and the evidence it collected.
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
Not counted
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.
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
Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.
Leaked records that mention jamesgreenblue.com, from OffSeq Breach.
No leaked records found
Breach holds no records for jamesgreenblue.com right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Automated reading of the public site. Ratings are indicative.
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
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with jamesgreenblue.com. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review jamesgreenblue.com.