Skip to main content

Security report for briancray.com

Brian Cray · Technology · N/a

Medium risk. 8 critical or high findings in Email security, Security headers and 2 other checks.

Security score

61/100

Risk levelMedium

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

The website briancray.com serves as a personal portfolio for Brian Cray, a front-end software engineer currently working at Apple and previously at Topsy. The site provides minimal content focused on professional background with links to LinkedIn and GitHub profiles, targeting technology professionals and recruiters. The business model is personal branding and showcasing open source contributions, positioning Brian as an individual professional within the technology sector. The domain is well-established since 2006, indicating a stable online presence. Technically, the website is built using Svelte framework with CSS styling and is hosted with Cloudflare DNS services. The site loads quickly and is mobile responsive at a basic level but lacks advanced SEO and accessibility features. No CMS or analytics tools are detected, and the site does not implement privacy or cookie policies. Security is adequate with HTTPS enabled and domain registration protections in place, but DNSSEC is not enabled and no security headers are present. From a security perspective, the site shows a moderate posture with no visible vulnerabilities or exposed sensitive data. However, the absence of privacy and cookie policies, security headers, and incident response information limits compliance and transparency. The lack of contact information and forms reduces potential attack surfaces but also limits user engagement and trust signals. Overall, the website is functional as a personal portfolio but would benefit from enhanced security practices, privacy compliance, and richer content to improve trustworthiness and professional presentation. Strategic improvements in security headers, DNSSEC, and policy disclosures are recommended to elevate the site's security and compliance posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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

8 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

  2. 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';…

  3. 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 briancray.com

This scan found 25 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. 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
72
Security headers
30
Email security
60
DNS health
80
Network security
100
GDPR outside view
25
Average
61

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

Brian Cray operates as an individual professional in the technology sector, focusing on front-end software engineering. The website acts as a digital resume and portfolio, linking to professional social profiles rather than offering commercial services. The market positioning is that of a skilled engineer with experience at notable companies like Apple and Topsy. Revenue streams are not applicable as this is a personal site. The target audience includes recruiters, peers, and open source collaborators. The site shows no evidence of partnerships or subsidiaries. Growth indicators are limited due to minimal content, but the long domain age suggests sustained professional activity. The ecosystem is limited to social media and open source platforms.

Security posture

The security maturity of briancray.com is moderate. HTTPS is enforced, and domain registration includes multiple prohibitive statuses to prevent unauthorized changes. However, the absence of DNSSEC and security headers such as Content-Security-Policy and Strict-Transport-Security reduces defense-in-depth. No privacy or cookie policies are present, indicating compliance gaps with GDPR and other regulations. Incident response and vulnerability disclosure mechanisms are not provided, limiting transparency and readiness. No analytics or tracking scripts reduce privacy risks but also limit user insights. Overall, the site is low risk but could improve security hygiene and compliance.

Recommendations

  1. Enable DNSSEC to enhance DNS security and prevent spoofing.
  2. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish privacy and cookie policies to improve GDPR compliance and user trust.
  4. Add contact information or a security contact channel to support incident response.
  5. Enhance SEO, accessibility, and content richness to improve user experience and professional presentation.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Brian Cray
Description
Personal website of a front-end software engineer for Apple, previously employed at Topsy. Provides links to LinkedIn and GitHub profiles showcasing employment history and open source work.
Key services
Software engineering expertise, Open source contributions
Content quality
basic
Branding
moderate

Technology

Stack
CSS, Cloudflare DNS
Frameworks
Svelte
Performance
fast
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled
  • Domain status includes clientDeleteProhibited and other EPP protections

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a minimal personal portfolio with limited content.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact information or forms present.
  4. Uses Cloudflare DNS but no DNSSEC.
  5. No security headers detected in HTML content.
  6. No analytics or tracking scripts detected.
  7. External links only to LinkedIn and GitHub profiles.
  8. No advertising or marketing tools detected.
Technical notes

Notes

The website uses a modern front-end framework (Svelte) with CSS for styling and is hosted with Cloudflare DNS services. The site is lightweight and loads quickly, indicating good performance. However, it lacks advanced SEO meta tags and accessibility features. No CMS or analytics platforms are detected, suggesting a simple static site architecture. The absence of security headers and DNSSEC represents technical debt in security configuration. The domain registration is stable and protected with multiple client-side prohibitions. Overall, the technical infrastructure is sound but could benefit from modernization in security and SEO practices.
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 briancray.com. 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 briancray.com.

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.