Skip to main content

Security report for perl.com

Technology · N/a

Medium risk. 6 critical or high findings in Email security, Security headers and 1 other check.

Security score

65/100

Risk levelMedium

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

Perl.com is a well-established online resource dedicated to the Perl programming language, offering news, tutorials, and community content since 1997. The website targets Perl developers and enthusiasts, providing valuable programming insights and fostering community engagement. The business model centers on content publishing and community support without direct commercial sales. Technically, the site is built using the Hugo static site generator, styled with Bootstrap, and employs Google Analytics and Tag Manager for visitor tracking. The site is mobile-optimized with good navigation and content relevance, though accessibility features are basic. From a security perspective, the website uses HTTPS and avoids exposing sensitive data, but lacks important security headers and explicit privacy or cookie policies. Contact information is limited to a GitHub issues page, with no direct emails or phone numbers provided. The absence of WHOIS registration data for the domain raises concerns about domain legitimacy and trustworthiness, despite the professional appearance and community trust signals on the site. Overall, Perl.com presents a solid content platform with moderate technical maturity and a generally safe user experience. However, the lack of domain registration transparency and formal privacy/security policies suggests areas for improvement to enhance trust and compliance.

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

    • 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

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

Keep watching perl.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. 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
85
Security headers
40
Email security
60
DNS health
70
Network security
100
GDPR outside view
35
Average
65

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

Perl.com occupies a niche position as a community-driven content hub for the Perl programming language, serving developers and open source contributors. Its competitive advantage lies in its long-standing presence and focused content on Perl culture and tooling. The site does not appear to monetize directly but benefits from sponsorships and community support, including ties to the Perl Foundation. The target audience is technical professionals and hobbyists interested in Perl. Growth indicators include regular article publishing and active community sponsorships. The partnership ecosystem includes recognized entities like the Perl Foundation and WebPros. Strategic observations highlight the need for improved transparency and formalization of privacy and security practices to maintain credibility.

Security posture

The website demonstrates a basic security posture with HTTPS enabled and no visible exposure of sensitive data. However, it lacks critical security headers such as Content-Security-Policy and X-Frame-Options, which are important for mitigating common web attacks. There is no evidence of a published security policy, incident response plan, or vulnerability disclosure mechanism. Contact channels for security issues are not provided. The absence of WHOIS data for the domain is a significant concern, potentially indicating registration or legitimacy issues. Compliance with GDPR and other data protection regulations is not clearly addressed, and cookie consent mechanisms are missing. Overall, the security maturity is moderate but requires enhancements to meet best practices and regulatory expectations.

Recommendations

  1. Implement and publish comprehensive privacy and cookie policies with explicit user consent mechanisms.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to improve protection against web vulnerabilities.
  3. Establish and disclose a formal security policy and incident response contact information to enhance trust and readiness.
  4. Verify and update domain WHOIS registration to ensure transparency and legitimacy, addressing the current lack of registration data.
  5. Improve accessibility compliance and consider adding a vulnerability disclosure policy or security.txt file to foster responsible security practices.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Since 1997 Perl.com has published articles about the Perl programming language, its culture and community.
Key services
Publishing articles about Perl programming, Community news and culture, Tutorials and tooling information
Content quality
good
Branding
consistent

Technology

Stack
Hugo 0.147.5, Bootstrap CSS, Google Analytics, Google Tag Manager
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • Use of HTTPS (implied by canonical URL https://www.perl.com/)
  • No visible exposed sensitive data
  • No vulnerable libraries detected in scripts

Analytics and tracking

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

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a content hub for Perl programming language news and tutorials
  2. No WHOIS data available, domain registration status unclear
  3. No explicit privacy, cookie, or terms of service policies found
  4. Contact is via GitHub issues, no direct email or phone contact found
  5. Uses Google Analytics and Tag Manager for tracking
  6. No security headers detected in HTML content
  7. No visible security or incident response policies
  8. Content is safe and appropriate for general audiences
  9. No WAF or blocking detected, full content accessible
Technical notes

Notes

The website is built using the Hugo static site generator, leveraging Bootstrap for responsive design and Google Analytics/Tag Manager for visitor tracking. The site structure is clear with good SEO meta tags and Open Graph data for social sharing. Performance is moderate, with asynchronous loading of analytics scripts. Accessibility is basic but could be improved. No CMS or dynamic backend detected, reducing attack surface but limiting interactive features. Hosting provider details are not disclosed. The technical stack is modern and appropriate for a content-focused site but lacks advanced security configurations and formal compliance features.
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 perl.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 perl.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.