Skip to main content

Security report for writing-readable-php.com

Technology · N/a

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

Security score

50/100

Risk levelMedium

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

The website 'Writing Readable PHP' is an educational platform focused on improving PHP code readability through tutorials and static analysis videos. It targets PHP developers and programmers seeking to write cleaner, more maintainable code. The business model revolves around providing high-quality educational content, likely monetized through video views or subscriptions, although no explicit monetization details are present. The site is relatively new, established in 2022, and appears to be a small-scale operation without extensive corporate backing or subsidiaries. Technically, the website employs standard web technologies including HTML5, JavaScript, Google Analytics, Google Tag Manager, and Font Awesome icons. Hosting is provided by DigitalOcean, a reputable cloud provider. The site demonstrates moderate performance and good mobile optimization, with basic accessibility and SEO optimizations. However, no CMS or advanced frameworks are detected, indicating a possibly custom or static site. From a security perspective, the site uses HTTPS with a valid SSL configuration and has domain transfer protections enabled. However, DNSSEC is not enabled, and no security headers were detected in the provided data, which could be improved. There are no visible forms or contact points for incident response or security policies, and privacy and cookie policies are absent, indicating gaps in compliance and transparency. Overall, the website is safe and suitable for general audiences, with no adult or questionable content. The lack of privacy and cookie policies, contact information, and security headers lowers its compliance and trustworthiness scores. Strategic improvements in these areas would enhance the site's security posture and user trust.

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. 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 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 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 writing-readable-php.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.

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
42
Security headers
50
Email security
60
DNS health
75
Network security
40
GDPR outside view
35
Average
50

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

The website positions itself as a niche educational resource for PHP developers focused on code readability and static analysis. Its competitive advantage lies in providing specialized, high-quality video content that appeals to developers seeking to improve coding standards. The business model appears content-driven, likely relying on audience engagement rather than direct sales. Target customers are individual developers and possibly small teams interested in clean coding practices. There is no evidence of partnerships, subsidiaries, or parent companies, suggesting an independent operation. Growth indicators are limited due to lack of business information. The site leverages common marketing tools like Google Analytics but lacks advanced business intelligence integrations or trust signals such as certifications or testimonials.

Security posture

The current security maturity level is moderate. The site benefits from HTTPS and domain transfer lock status, which protect against common threats. However, the absence of DNSSEC, security headers, and incident response contact information indicates room for improvement. No vulnerabilities or exposed sensitive data were detected in the provided content. Compliance gaps exist due to missing privacy and cookie policies, which are critical under GDPR and similar regulations. The lack of a vulnerability disclosure or security.txt file reduces transparency and user confidence in security practices. Overall, the security culture appears basic, with no advanced protections or documented policies.

Recommendations

  1. Enable DNSSEC to enhance domain name system security.
  2. Implement standard security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  3. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements.
  4. Add clear contact information including emails and phone numbers for general and security incident reporting.
  5. Consider adding a vulnerability disclosure policy or security.txt file to improve transparency and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Learn how to write code that’s a joy to read for you, your co-workers, and future self. View high-quality videos on both clean coding and static analysis.
Key services
High-quality videos on clean coding, Static analysis tutorials
Content quality
good
Branding
consistent

Technology

Stack
HTML5, JavaScript, Google Analytics, Google Tag Manager, Font Awesome
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled
  • Domain status clientTransferProhibited

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is an educational resource focused on PHP code readability.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails, phone numbers, or physical addresses found.
  4. Uses Google Analytics and Tag Manager for tracking.
  5. Hosted on DigitalOcean with domain registered via Registrar.eu.
  6. No visible security headers detected in provided data.
  7. No forms detected in the provided HTML snippet.
  8. No social media links explicitly found in the provided content.
  9. Content is safe and suitable for general audiences.
Technical notes

Notes

The website uses a straightforward technical infrastructure with HTML5, JavaScript, and common libraries like Font Awesome. It integrates Google Analytics and Tag Manager for tracking and marketing purposes. Hosting on DigitalOcean suggests reliable infrastructure. Performance is moderate with good mobile optimization, but accessibility features are basic. No CMS or advanced frameworks were detected, indicating a lightweight or custom-built site. The absence of security headers and DNSSEC represents technical debt and potential risk. SEO is adequately addressed through meta tags and canonical links. Overall, the technical stack is modern but could benefit from enhanced security and accessibility improvements.
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 writing-readable-php.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 writing-readable-php.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.