Skip to main content

Security report for lexfridman.com

Lex Fridman · Technology · United States

High risk. 10 critical or high findings in Network security, Security headers and 3 other checks.

Security score

42/100

Risk levelHigh

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

Lex Fridman's website serves as a professional platform showcasing his research work, educational lectures, and podcast content. The site targets an audience interested in AI, autonomous vehicles, and machine learning, including researchers, students, and technology enthusiasts. The business model revolves around personal branding, educational dissemination, and merchandise sales, supported by a strong academic affiliation with MIT. The website is well-structured with rich content, including research publications and media links, establishing a credible presence in the technology and education sectors. Technically, the site is built on WordPress using a child theme of Twenty Twelve, enhanced with SEO plugins and Google Analytics for tracking. The infrastructure is modern and moderately optimized for performance and mobile responsiveness. Accessibility is basic but functional. Security practices include HTTPS enforcement and safe handling of external links, though advanced security headers are missing. Privacy compliance is lacking due to the absence of privacy and cookie policies. The security posture is solid with no critical vulnerabilities detected, but improvements are recommended in privacy policy publication, cookie consent mechanisms, and security header implementation. The domain registration is consistent with the website's claims, indicating legitimacy and trustworthiness. Overall, the site is professional and trustworthy but would benefit from enhanced privacy and security compliance to meet modern standards.

Scanned

NIS2 and GDPR posture

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

10 findings rated critical or high. Fix these first.

  1. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

  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

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

Keep watching lexfridman.com

This scan found 26 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
57
Security headers
15
Email security
85
DNS health
60
Network security
0
GDPR outside view
35
Average
42

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 · found on this site
  • 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

Lex Fridman holds a strong position as an AI researcher and educator affiliated with MIT, leveraging his personal brand through multiple channels including research publications, podcasts, and educational content. The business model is focused on knowledge sharing and community engagement rather than direct commercial sales, although a merchandise store exists. The target market includes academia, AI practitioners, and technology enthusiasts. The website's integration with scholarly platforms like Google Scholar and research repositories enhances credibility. Growth indicators include active podcasting and educational outreach. Partnerships appear limited to academic and educational domains, with no commercial subsidiaries or parent companies identified.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and safe external link handling. However, it lacks explicit security headers such as Content-Security-Policy and X-Frame-Options, which could mitigate certain attack vectors. No privacy policy or cookie consent mechanisms are present, representing compliance gaps with GDPR and other privacy regulations. There is no public incident response or vulnerability disclosure information, which could impact trust in case of security incidents. Overall, the site is secure for general use but should enhance privacy and security transparency to align with best practices.

Recommendations

  1. Publish a comprehensive privacy policy detailing data collection and user rights.
  2. Implement a cookie consent banner to comply with GDPR and other privacy laws.
  3. Add security headers like Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Provide clear incident response and vulnerability disclosure contact information.
  5. Regularly audit third-party scripts and analytics for privacy compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Lex Fridman
Description
Research Scientist at MIT focusing on autonomous vehicles, human-robot interaction, and machine learning. Host of the Lex Fridman Podcast. Provides educational content and research publications.
Key services
Research publications, Educational lectures, Podcast hosting, Merchandise sales
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, Yoast SEO, Google Analytics (MonsterInsights), jQuery, Tingle.js modal library
Frameworks
WordPress theme: Twenty Twelve and child theme
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced with forceSSL in Google Analytics config
  • External links open in new windows with noopener noreferrer
  • Google Analytics opt-out mechanism implemented

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Marketing tools
MonsterInsights Google Analytics plugin
Transparency
basic

Site quality

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

Key observations

  1. Website is a personal academic and media platform for Lex Fridman.
  2. Content is rich with research publications, podcast links, and educational resources.
  3. No explicit privacy or cookie policies found, which is a compliance gap.
  4. Uses HTTPS and standard security practices but lacks advanced security headers.
  5. No contact emails or phone numbers explicitly listed; contact form is available.
  6. Social media presence is strong and linked clearly.
  7. No signs of malicious or suspicious activity detected.
Technical notes

Notes

The website uses a WordPress CMS with a child theme based on Twenty Twelve, supported by plugins such as Yoast SEO and MonsterInsights for analytics. The tech stack includes jQuery and Tingle.js for UI components. Performance is moderate with asynchronous loading of analytics scripts and deferred navigation scripts. Mobile optimization is good, though accessibility features are basic. SEO is enhanced by meta tags and structured data (JSON-LD). Hosting details are not explicit but the site uses HTTPS with a valid SSL certificate. There is room for modernization by adopting newer frameworks or improving accessibility and security headers.
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 lexfridman.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 lexfridman.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.