Homeβ€Ί Infrastructureβ€Ί prod-cdn-media-api.livescore.com
This site failed important safety checks β€” please read this before going any further.
Be careful β€” Suspicious

No β€” prod-cdn-media-api.livescore.com doesn't look safe

35/ 100 trust score
Industry: Infrastructure Checked Jul 12, 2026 Infrastructure average: 45 27 signals

In plain English

This subdomain for livescore.com currently returns a 404 error and shows almost no signals of an active, maintained service. The WHOIS record is hidden, there's no contact info, and the entire setup feels incomplete or abandoned. Unless you know for certain that this is a stale internal endpoint, it's best to steer clear.

What you should do now

Don't panic. These steps limit the damage, and the sooner you take them the better.

1

Don't enter any details

No passwords, card numbers or personal information β€” even if the site looks professional.

2

Close the tab

Especially if you got here from an email, text message or social media ad.

3

Already paid? Call your bank

Contact your bank or card provider right away. They can often stop or reverse a recent payment.

4

Warn others

Report the site and share this check with anyone who sent you the link.

N Partner pick
Better safe than sorry. Stay covered everywhere: NordVPN's Threat Protection blocks known scam sites before they load.
Try NordVPN β†’
Cross-referenced 27 live signals from Google Safe Browsing, VirusTotal, WHOIS and more on Jul 12, 2026. How we score β†’

Where the score comes from

We look at six areas. Here's how prod-cdn-media-api.livescore.com did in each.
60
Security

The site uses a valid SSL certificate from a trusted issuer and doesn't appear on any threat lists. But it lacks basic browser protections like clickjacking prevention, which is a minor gap for an API endpoint that isn't serving user-facing content.

40
Identity

WHOIS data returns no match for this subdomain, which means the registrant information is hidden or the domain isn't properly registered. Combined with no contact details or brand identity, this is a significant gap for any site that claims to be part of an established service.

50
Reputation

The domain isn't blacklisted, but it has no history in the Wayback Machine and no external trust signals like a Trustpilot profile. That's not unusual for a small or new technical endpoint, but the complete lack of a track record makes it hard to verify.

50
Transparency

There's no about page, no contact information, and no social media presence. While a bare API subdomain doesn't need the transparency of a consumer website, the total absence is still a yellow flag when you're expecting a legitimate service backend.

60
Compliance

No privacy policy or terms of service are published here. Since this is an infrastructure endpoint rather than a consumer-facing site, missing legal pages is less concerning, but it would be a real issue if the endpoint were involved in data processing.

50
Infrastructure

The site loads quickly on Google Cloud infrastructure with modern TLS, but it returns a 404 error and lacks DNSSEC, basic security headers, and email handling capabilities. The 404 suggests the endpoint is either misconfigured or intentionally deactivated.

What we checked

The 27 signals behind this report.
Security & Transport
Certificate Issuer
Google Trust Services
Google Web Risk
Clean
SSL Certificate
Valid
Security Headers
0 of 6
Server
nginx
TLS Version
TLS 1.3
Identity & WHOIS
About Page
Not found
Branding
Missing
Business Disclosure
Not found
Contact Info
Not found
Legal Pages
Missing
Infrastructure & DNS
DNS Blacklists
Clean
DNS Resolution
1 IP(s)
DNSSEC
Not enabled
Email (MX Records)
None
Hosting Network (ASN)
AS396982 GOOGLE-CLOUD-PLATFORM
Page Load Time
34ms
Reputation & Reach
Page Heading
404 Not Found
Page Title
404 Not Found
Sitemap
Not found
Social Media Presence
None found
Structured Data
None found
Tranco Rank
Not ranked
Trustpilot
No Trustpilot profile
Web Archive History
No archive found
Website Status
HTTP 404
robots.txt
Not found

Think this verdict is wrong?

Site owners can request a fresh scan. Scores update automatically as signals change.

When you check a subdomain like prod-cdn-media-api.livescore.com, you're really asking whether the underlying service is trustworthy. In this case, the answer is complicated. The subdomain is clearly part of the larger livescore.com infrastructure β€” a well-known live sports score service β€” but this particular endpoint is not functioning. It returns a 404 error and shows no signs of active use: no contact details, no legal pages, and no record in the Wayback Machine.

For an API endpoint, a certain level of opacity is normal. But the hidden WHOIS information combined with the broken response raises a question: is this a retired service, a misconfigured server, or something else? Without the ability to confirm who runs it or why it's offline, the safest approach is to avoid relying on it. If you're a developer considering integration, you'd want to reach out to the parent company directly and confirm that this subdomain is still intended for use. At the moment, there isn't enough evidence to call it a scam, but there's also little reason to trust it as an active service.

Ultimately, prod-cdn-media-api.livescore.com looks like a dead endpoint. The signals suggest it's not a threat, but it's also not a functioning part of the livescore platform. For now, treat it as a domain to avoid until it shows signs of life or the parent company provides clarity.

More Infrastructure sites

How similar sites score. See all β†’