When you visit breproxy.pierpass-tmf.org, you get a 404 error — the site simply doesn't serve content. That alone is a red flag if you were expecting a working proxy or API endpoint. The domain name references PierPass, a real organization in the container terminal industry, but the subdomain breproxy has no public documentation, no contact information, and no way to verify ownership. The WHOIS record is blocked, so we can't even confirm who registered it. For an infrastructure service, you'd normally see at least a status page or support contact. Without that, there's no way to tell if this is a legitimate internal tool gone dark or a parked domain with no purpose. Our advice: find a verified source for any PierPass-related service directly from their main website, not from an unlisted subdomain. If someone sent you here, treat it with caution. The technical setup is fine (SSL, Azure hosting), but a missing page and invisible owner make this impossible to recommend.
No — breproxy.pierpass-tmf.org doesn't look safe
In plain English
This site isn't even loading — it returns a 404 error, which means there's nothing to interact with. Combined with a complete lack of ownership info, no contact details, and no history anywhere, there's no reason to trust it. If you were expecting to find a working service here, you should look for an official source instead.
What you should do now
Don't panic. These steps limit the damage, and the sooner you take them the better.
Don't enter any details
No passwords, card numbers or personal information — even if the site looks professional.
Close the tab
Especially if you got here from an email, text message or social media ad.
Already paid? Call your bank
Contact your bank or card provider right away. They can often stop or reverse a recent payment.
Warn others
Report the site and share this check with anyone who sent you the link.
Where the score comes from
The site has a valid SSL certificate and modern TLS, plus a content security policy. No malware or blacklist flags. Missing a few basic browser protections, but nothing alarming for a non-public-facing service.
Who owns this domain? The WHOIS query returned a malformed request, so we have no ownership details. Combined with no archive history and no age data, there's essentially no way to verify who is behind this subdomain.
No blacklists or Google threats, but also no positive track record. The site has no history in the Wayback Machine and is not ranked among top sites. This is a neutral signal: not harmful, but not proven either.
A complete lack of contact info, about page, or social media presence. Even for a technical service, you'd expect some way to reach the operator. The missing favicon and branding add to the opaque feel.
No privacy policy or terms of service anywhere. For a proxy service that might handle data, this is a gap. However, since the site currently returns a 404 error, it's not actively collecting anything right now.
DNS resolves, SPF is set, and the site is hosted on Microsoft Azure, a reputable provider. SSL and TLS are solid. Missing DNSSEC is minor. Overall technically functional, but the site doesn't serve content.
What we checked
Think this verdict is wrong?
Site owners can request a fresh scan. Scores update automatically as signals change.