Skip to main content

Security report for t-mobile.com

T-Mobile · Telecommunications · United States

Medium risk. 5 critical or high findings in Security headers and GDPR outside view.

Security score

59/100

Risk levelMedium

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

T-Mobile is a leading telecommunications provider in the United States, operating as a subsidiary of Deutsche Telekom AG. The company offers wireless voice, messaging, and data services targeting both consumers and businesses. The domain t-mobile.com is mature and well-registered, reflecting the company's long-standing market presence. However, the website content is currently inaccessible due to a Web Application Firewall (WAF) or security blocking mechanism, which prevents a full assessment of the site's content and user experience. From a technical perspective, the website is hosted on Akamai's edge network, but the SSL/TLS configuration is critically lacking, with no valid certificate or enabled protocols detected. This severely impacts the security posture and user trust. The presence of strict transport security headers indicates some security awareness, but the absence of HTTPS negates these benefits. No privacy, cookie, or terms of service policies are visible, and no contact information or forms are accessible in the provided content. Security-wise, the site suffers from critical vulnerabilities due to missing SSL/TLS, lack of modern protocols, and no certificate transparency compliance. The domain registration is consistent and trustworthy, with strong domain protection and no suspicious WHOIS patterns. Overall, the website's security posture is poor, and the content blockage further limits analysis. Strategic recommendations include immediate installation of a valid SSL certificate, enabling modern TLS protocols, enhancing security headers, and ensuring accessibility of privacy and contact information. Addressing these issues will improve trust, compliance, and user experience significantly.

Scanned

This is an earlier scan of t-mobile.com. View the latest report

NIS2 and GDPR posture

GDPR outside view
40/ 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. 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 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';…

  2. 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 t-mobile.com

This scan found 16 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
50
Security headers
30
Email security
50
DNS health
85
Network security
100
GDPR outside view
40
Average
59

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

T-Mobile holds a strong position in the US telecommunications market as a major wireless carrier. Its business model focuses on providing mobile voice and data services, device sales, and business solutions. The company benefits from its parent Deutsche Telekom AG's global presence and resources. The domain's mature registration supports the company's established market presence. However, the current website access restrictions and lack of visible policies or contact details limit customer engagement and transparency. The company likely leverages Akamai for content delivery and security, but the current SSL/TLS misconfiguration is a critical operational risk. No direct evidence of partnerships or subsidiaries beyond the parent company was found in the provided data.

Security posture

The security posture of the website is currently weak due to the absence of a valid SSL certificate and disabled TLS protocols, which are fundamental for secure communications. Although the strict transport security header is present, it cannot function properly without HTTPS. The lack of OCSP stapling, session resumption, and certificate transparency compliance further degrade security. The website is protected by a WAF or similar security mechanism, which blocks access and prevents content scraping, indicating some level of security control. However, the inability to serve secure content undermines user trust and exposes the site to potential interception risks. No evidence of incident response contacts or security policies was found, suggesting gaps in transparency and readiness.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the site.
  2. Enable modern TLS protocols (TLS 1.2 or higher) and strong cipher suites to secure communications.
  3. Implement OCSP stapling and session resumption to improve security and performance.
  4. Publish clear privacy, cookie, and terms of service policies accessible to users.
  5. Provide visible contact information including security incident response channels to enhance trust.
Technical notes

Notes

The website is hosted on Akamai's edge network, indicating use of a major CDN and security provider. However, the SSL/TLS configuration is critically deficient with no valid certificate or enabled protocols detected, resulting in no HTTPS availability. The HTTP headers include strict transport security directives, but these are ineffective without HTTPS. The DNS records show a mature and well-managed domain with multiple authoritative name servers and no DNSSEC enabled. The site currently returns an Access Denied error page with minimal HTML content, indicating a WAF or security blocking mechanism is active. Performance metrics are unavailable due to blocked content. No CMS, frameworks, or client-side technologies could be identified from the limited HTML content.
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

Earlier scans of this domain

  1. 72/100Medium27 findingsView report
Reviews of this site

Share your experience with t-mobile.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 t-mobile.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.