Skip to main content

Security report for testandcode.com

Technology · N/a

Medium risk. 6 critical or high findings in GDPR outside view and SSL/TLS.

Security score

68/100

Risk levelMedium

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

Test & Code is a specialized podcast website focused on Python testing and software engineering topics, hosted by Brian Okken. The site offers podcast episodes and educational pytest courses, targeting Python developers and software engineers interested in automated testing. The business operates in the technology sector with a niche market position and a small-scale operation founded in 2016. The website demonstrates excellent content quality, consistent branding, and strong trust indicators such as a long domain age and professional podcast hosting via Transistor.fm. Technically, the site uses modern web technologies including Alpine.js and is hosted on Transistor.fm's platform. It is well-optimized for mobile devices, has good accessibility and SEO practices, and loads quickly. The site includes CSRF tokens indicating some security awareness but lacks several security headers and DNSSEC is not enabled, representing areas for improvement. From a security perspective, the site uses HTTPS and shows no signs of vulnerabilities or malicious content. However, it lacks privacy and cookie policies, terms of service, and incident response information, which are important for compliance and user trust. No contact emails or phone numbers are explicitly provided, limiting direct communication channels. Overall, the website is professional, trustworthy, and focused on delivering quality podcast content. Strategic recommendations include publishing privacy and cookie policies, adding security headers, enabling DNSSEC, and providing clear contact and security incident response information to enhance compliance and security posture.

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

6 findings rated critical or high. Fix these first.

  1. 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

    • 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

    • High

      Third-party services without privacy policy

      Detected services: LinkedIn, YouTube

      What to do: Document all third-party data sharing in your privacy policy

  2. 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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching testandcode.com

This scan found 22 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
52
Security headers
80
Email security
70
DNS health
70
Network security
100
GDPR outside view
35
Average
68

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 testandcode.com, from OffSeq Breach.

No leaked records found

Breach holds no records for testandcode.com 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

The business operates as a content creator and educator in the Python testing niche, leveraging podcast episodes and paid pytest courses as revenue streams. Its market positioning is strong within the Python developer community, supported by a consistent brand and active social media presence across YouTube, LinkedIn, Mastodon, and Bluesky. The absence of direct contact information suggests a focus on content delivery rather than direct sales or support. The partnership with Transistor.fm for hosting indicates a reliance on specialized podcast infrastructure. Growth indicators include regular episode releases and a supporter base via Patreon. The business model is primarily educational and community-driven, targeting software engineers interested in improving testing practices.

Security posture

The website demonstrates a moderate to good security maturity level. HTTPS is enforced, and CSRF tokens are implemented, which protect against common web vulnerabilities. However, the absence of key security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces the overall security posture. DNSSEC is not enabled, which could improve DNS security. There is no published security policy, incident response plan, or vulnerability disclosure mechanism, which are important for transparency and compliance. No sensitive data exposure or vulnerable libraries were detected. The lack of privacy and cookie policies indicates compliance gaps, particularly with GDPR. Overall, the site is secure for its purpose but could benefit from enhanced security controls and compliance documentation.

Recommendations

  1. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements.
  2. Implement and enable DNSSEC for the domain to enhance DNS security.
  3. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Create and publish a security policy and incident response plan, including contact channels for security issues.
  5. Provide clear contact information for business and security inquiries to improve trust and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
The Python Testing Podcast hosted by Brian Okken. Software engineering is more fun with automated testing. Topics include pytest, packaging, engineering models, project tooling, and related subjects.
Key services
Podcast episodes on Python testing, Educational pytest courses
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Alpine.js, Transistor.fm podcast hosting, CSS, HTML5
Frameworks
Alpine.js
Platforms
Transistor.fm
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (implied by URL)
  • CSRF tokens present in meta tags

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a professional podcast site focused on Python testing.
  2. No privacy, cookie, or terms of service pages found.
  3. No contact emails or phone numbers explicitly listed.
  4. Social media presence is strong with multiple platforms linked.
  5. No forms detected on the main page; no data collection forms present.
  6. No security.txt or vulnerability disclosure found.
  7. CSRF tokens present indicating some security awareness.
  8. No advertising or tracking scripts detected.
  9. Site uses modern JavaScript framework Alpine.js and is hosted on Transistor.fm.
  10. No suspicious or malicious content detected.
Technical notes

Notes

The website is built using modern web technologies including Alpine.js for interactivity and is hosted on Transistor.fm, a specialized podcast hosting platform. The site uses valid HTML and CSS, includes meta tags for SEO and social media sharing (Open Graph and Twitter cards), and is optimized for mobile devices with responsive design. Performance is fast with minimal external dependencies. No common CMS was detected, indicating a custom or static site approach. The site lacks some advanced security headers and DNSSEC, which are recommended for technical hardening. No analytics or tracking scripts were identified, suggesting minimal user tracking. Overall, the technical infrastructure is solid, modern, and well-suited for podcast content delivery.
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 testandcode.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 testandcode.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.