usdtr.bid is registered with whois.nic.bid and is hosted on AS24940 Hetzner Online GmbH in Finland. We couldn't read an SSL certificate for it when we last analysed it.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
We couldn't read an SSL certificate on port 443 when we last analysed usdtr.bid. Refresh the analysis to check again.
Is usdtr.bid’s name taken on other extensions?
Every IP address usdtr.bid resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| usdtr.bid | 65.108.205.61 | 600 |
| Host | Name server | TTL |
|---|---|---|
| usdtr.bid | ns7.alidns.com | 21600 |
| usdtr.bid | ns8.alidns.com | 21600 |
| Host | Start of authority | TTL |
|---|---|---|
| usdtr.bid | ns7.alidns.com hostmaster.hichina.com 2025042409 3600 1200 86400 600 | 600 |
Other domains served from 65.108.205.61. Normal for shared hosting and CDNs.
No reviews yet. Used usdtr.bid? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
usdtr.bid has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
usdtr.bid is registered through whois.nic.bid. See WHOIS →
usdtr.bid is served from 1 IP address, mainly on AS24940 Hetzner Online GmbH in Finland. See Hosting →
Raw registry data for usdtr.bid. May be redacted by privacy services.
Number of allowed queries exceeded.
The first response from http://www.usdtr.bid, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with usdtr.bid. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.