Skip to main content

Security report for postoffice.co.uk

Post Office Limited · Transportation · United Kingdom

Medium risk. 5 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

53/100

Risk levelMedium

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

Post Office Limited operates a comprehensive UK-wide network providing postal, financial, travel, insurance, and identity services. The website reflects a mature digital presence with extensive service offerings and strong brand consistency. The company leverages multiple external partners for financial and travel services, integrating them seamlessly into their platform. Technically, the site uses Magnolia CMS, Akamai CDN, and common JavaScript libraries like jQuery, ensuring a robust infrastructure. However, the SSL/TLS configuration is critically flawed with an invalid certificate and no enabled TLS protocols, exposing users to security risks. Additionally, a subdomain takeover vulnerability exists on api.postoffice.co.uk, which could be exploited if not remediated. Privacy and cookie policies are comprehensive and GDPR compliant, supporting strong privacy practices. Overall, the site is professional and trustworthy but requires urgent security improvements to protect user data and maintain trust.

Scanned

NIS2 and GDPR posture

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

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

  4. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Potential Subdomain Takeover

      Subdomain api.postoffice.co.uk points to unregistered service d-j3tivlq9bg.execute-api.eu-west-2.amazonaws.com

      What to do: Remove or fix CNAME record to prevent subdomain takeover

      • WSTG-CONF-10
      • NIS2 21(2)(i)
      • IR 2024/2690 12.4: Implementing Regulation (EU) 2024/2690, Annex point 12.4: Asset inventory
      • NIST CM-8: NIST SP 800-53 Rev. 5 CM-8: System Component Inventory

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

Keep watching postoffice.co.uk

This scan found 15 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
0
Security headers
70
Email security
50
DNS health
65
Network security
100
GDPR outside view
33
Average
53

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 Post Office holds a strong market position as a national essential service provider in the UK, with a diversified business model spanning postal, financial, travel, and insurance sectors. Its extensive branch network and online presence cater to a broad customer base including individuals and businesses. Partnerships with Capital One, Western Union, and Holiday Extras enhance its service portfolio and revenue streams. The company demonstrates strategic use of digital tools for customer engagement and service delivery. Growth opportunities exist in further digital transformation and security enhancements to maintain competitive advantage and customer trust.

Security posture

The website exhibits a moderate security maturity level with standard security headers implemented. However, the invalid SSL certificate and lack of TLS support represent critical vulnerabilities that undermine secure communications. The detected subdomain takeover risk further exposes the organization to potential attacks. Absence of explicit security policies and incident response contacts on the site indicates gaps in security governance and transparency. While privacy compliance is strong, the overall security posture requires immediate remediation of SSL/TLS issues and proactive vulnerability management to reduce business risk.

Recommendations

  1. Immediately renew and correctly configure SSL certificates to enable HTTPS with modern TLS protocols.
  2. Mitigate the subdomain takeover vulnerability on api.postoffice.co.uk by properly configuring or removing unused DNS entries.
  3. Publish a clear security policy and incident response contact information to improve transparency and trust.
  4. Implement a security.txt file to facilitate responsible vulnerability disclosure.
  5. Regularly audit and update security headers and practices to align with industry best practices.

Contact details published on the site

Addresses
Legal name
Post Office Limited
Technical notes

Notes

The website is built on Magnolia CMS and served via Akamai CDN, ensuring scalability and performance. Use of jQuery and custom JavaScript supports interactive features such as search and forms. External integrations with financial and travel partners are well embedded. Despite these strengths, the SSL/TLS configuration is severely lacking, with no valid certificate and no enabled TLS versions, which is a critical technical risk. Performance data is unavailable, but the use of CDNs and modern web design suggests moderate to good performance. Accessibility and SEO optimizations are evident through ARIA roles, structured data, and meta tags. Technical debt appears low but security misconfigurations pose a significant operational risk.
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 postoffice.co.uk. 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 postoffice.co.uk.

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.