54789.blog is hosted on AS8075 Microsoft Corporation in Hong Kong. Its SSL certificate from Let's Encrypt expired on 21 Jul 2025, and the site does not support HTTP/3.
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.
Is 54789.blog’s name taken on other extensions?
Every IP address 54789.blog resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| pgl.6cdn.net | 20.2.24.45 | 300 |
| pgl.6cdn.net | 20.255.153.77 | 300 |
| pgl.6cdn.net | 52.175.23.235 | 300 |
| pgl.6cdn.net | 52.184.64.141 | 300 |
| pgl.6cdn.net | 52.184.70.92 | 300 |
| Host | Points to | TTL |
|---|---|---|
| 54789.blog | pgl.6cdn.net | 600 |
| Host | Name server | TTL |
|---|---|---|
| 54789.blog | ns1.dnsip.com | 21600 |
| 54789.blog | ns2.dnsip.com | 21600 |
| Host | Start of authority | TTL |
|---|---|---|
| 54789.blog | ns1.dnsip.com dnsadmin.dnsip.com 1745317712 7200 3600 1209600 1800 | 600 |
Other domains served from 52.184.64.141. Normal for shared hosting and CDNs.
No reviews yet. Used 54789.blog? 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.
54789.blog has no community safety rating yet. Its SSL certificate expired on 21 Jul 2025. See Security →
54789.blog is served from 5 IP addresses, mainly on AS8075 Microsoft Corporation in Hong Kong. See Hosting →
The first response from http://www.54789.blog, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with 54789.blog. 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.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.