Skip to main content

Security report for afeld.me

Aidan Feldman · Technology · United States

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

66/100

Risk levelMedium

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

The website afeld.me serves as a comprehensive personal professional portfolio for Aidan Feldman, a seasoned web developer, educator, and community organizer with extensive experience in government technology and civic tech. The site highlights his freelance consulting services, teaching roles at prestigious universities, and active participation in open source projects and community events. The content is well-structured and detailed, targeting developers, government and non-profit technology teams, and students interested in technology and public policy. Technically, the website employs modern web technologies including HTML5, CSS, JavaScript, and popular libraries such as jQuery and Autolinker. It leverages CDN-hosted assets for performance and uses Google Analytics for visitor tracking. The site is hosted with Cloudflare DNS and registrar services, ensuring reliable uptime and fast delivery. Mobile optimization and SEO practices are adequately implemented, providing a good user experience across devices. From a security perspective, the site enforces HTTPS and has domain transfer protections in place. However, it lacks DNSSEC, security headers, and formal privacy or cookie policies, which are important for compliance and enhanced security posture. No forms or sensitive data collection mechanisms are present, reducing attack surface. The WHOIS data is consistent with the website's professional identity, showing a long-standing domain registration aligned with the owner's history. Overall, the website presents a high level of professionalism and trustworthiness with minor gaps in privacy compliance and security hardening. Strategic improvements in policy publication and security headers would elevate the site's compliance and security stature.

Scanned

NIS2 and GDPR posture

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

5 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. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching afeld.me

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. 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
75
Security headers
30
Email security
70
DNS health
70
Network security
100
GDPR outside view
53
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 afeld.me, from OffSeq Breach.

No leaked records found

Breach holds no records for afeld.me 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

Aidan Feldman operates as an independent technologist and educator with a strong foothold in government and civic technology sectors. His business model revolves around freelance consulting, teaching at universities, and contributing to open source projects. The target market includes government agencies, non-profits, educational institutions, and technology professionals seeking expertise in DevSecOps, cloud infrastructure, and software compliance. The site demonstrates a mature personal brand with a consistent online presence across multiple professional and social platforms. There is no indication of a parent company or subsidiaries, emphasizing a solo professional operation. The extensive experience with federal agencies and civic tech organizations positions him as a trusted expert in his niche. The lack of commercial advertising or e-commerce elements suggests a service and knowledge-sharing focus rather than product sales.

Security posture

The website benefits from HTTPS encryption and domain transfer protection, which are foundational security measures. The absence of DNSSEC is a notable gap that could expose DNS spoofing risks. No security headers such as Content-Security-Policy or X-Frame-Options were detected, which could mitigate certain web-based attacks. The site does not collect user input via forms, reducing exposure to injection or data leakage vulnerabilities. Google Analytics is used for tracking without visible cookie consent, which may raise privacy compliance concerns. No vulnerability disclosure or incident response information is published, limiting transparency for security issues. Overall, the security posture is solid but could be enhanced by implementing DNSSEC, security headers, and formal privacy and vulnerability disclosure policies.

Recommendations

  1. Enable DNSSEC on the domain to strengthen DNS security and prevent spoofing.
  2. Implement standard security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to protect against common web vulnerabilities.
  3. Publish a comprehensive privacy policy and cookie policy to improve GDPR and privacy compliance.
  4. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
  5. Incorporate a cookie consent mechanism to comply with privacy regulations and inform users about tracking.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Aidan Feldman
Description
Web developer by day, dancer by night.
Key services
Freelance technology consulting, Teaching and curriculum development, Community organizing, Open source contributions
Content quality
excellent
Branding
consistent

Technology

Stack
HTML5, CSS, JavaScript, jQuery, Autolinker, JSONPanel, Google Analytics (gtag.js)
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Domain status clientTransferProhibited
  • No exposed sensitive data in HTML content

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
excellent
Navigation
good
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is a personal professional portfolio for Aidan Feldman, a web developer and educator.
  2. Content is rich, detailed, and well-structured with extensive professional experience and teaching credentials.
  3. No privacy or cookie policies found, which is a compliance gap.
  4. No forms detected on the site; minimal data collection beyond analytics.
  5. Uses modern JavaScript libraries and CDN-hosted assets.
  6. Google Analytics is used for visitor tracking without visible cookie consent mechanism.
  7. No security.txt or vulnerability disclosure policy found.
  8. Domain is registered with Cloudflare and uses Cloudflare DNS but DNSSEC is not enabled.
  9. No security headers detected in the HTML content provided.
  10. No signs of malware, phishing, or suspicious content.
Technical notes

Notes

The website is built with clean, modern HTML and CSS, enhanced by JavaScript libraries including jQuery and Autolinker for dynamic content rendering and linkification. It uses JSONPanel for structured data display. Assets are served via jsDelivr CDN, ensuring fast load times and reliability. Google Tag Manager and Google Analytics are integrated for visitor analytics. The site is hosted with Cloudflare DNS and registrar services, providing robust infrastructure and protection against common network attacks. Mobile responsiveness is good, and SEO meta tags are properly configured. No CMS or backend platform is detected, indicating a static or custom-built site. The technical implementation is solid with opportunities for improved security hardening and privacy compliance.
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 afeld.me. 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 afeld.me.

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.