If you landed on tce.query.api.dvb.corpinter.net expecting a normal website, you probably got a 400 error instead. That's because this is a backend API endpoint, not a page for humans. It requires a client certificate to connect — a common security setup for internal services. There are no signs of scams or malware: the SSL certificate is valid, the host is Microsoft Azure, and no blacklists have flagged it. Because it's not a consumer-facing business, you won't find an about page, privacy policy, or contact info — and that's fine. The important thing is that the site itself is not dangerous. If you don't have a specific reason to call this API, you can safely ignore it. For developers who do need to use it, the certificate requirement is a good sign that the service is locked down properly.
Yes — tce.query.api.dvb.corpinter.net looks mostly safe
In plain English
This isn't a consumer website — it's a technical API endpoint that returns a 400 error unless you send a valid client certificate. That's a security feature, not a flaw. The site is hosted on Microsoft Azure with a clean reputation and no malware flags. Unless you need to interact with this API directly, there's no reason for concern.
Where the score comes from
The site uses a valid SSL certificate from a trusted issuer and is on a modern connection. No malware or phishing flags are present. The 400 error you see is actually a security measure: it requires a client certificate to proceed, which is standard for protected APIs.
The subdomain does not appear in public WHOIS records, which is normal for a technical endpoint. The main domain behind it isn't visible here, so there's no way to confirm who runs this service. For an internal API, that's not alarming, but it does mean you can't easily verify ownership.
No blacklists or Google Safe Browsing flags exist. The site has no history in the Wayback Machine, but that's expected for an API that requires authentication to crawl. Overall, there are no external signals of abuse.
There is no public contact page, about page, or social media presence. For a technical API endpoint that isn't meant for consumers, this is completely normal. You wouldn't expect a customer service line for a server-to-server service.
No privacy policy, terms of service, or cookie consent are present. This endpoint is not a commercial website targeting consumers, so legal disclosures aren't applicable. There's no compliance risk here.
The endpoint is hosted on Microsoft Azure, a reputable cloud provider, and resolves quickly. It doesn't handle email (no MX records), which is fine for an API. DNSSEC is not enabled, but that's common for subdomains.
What we checked
Run this site? Show your score.
Add a trust badge so visitors can see your live score for themselves.
Get your badge →