gomsajang.com is hosted on AS4766 Korea Telecom in Korea (the Republic of). Its SSL certificate from Amazon expired on 14 Mar 2026, 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 gomsajang.com’s name taken on other extensions?
Every IP address gomsajang.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| gomsajang.com | 183.111.139.229 | 1800 |
| gomsajang.com | 203.245.12.108 | 1800 |
| gomsajang.com | 203.245.12.115 | 1800 |
| gomsajang.com | 203.245.12.122 | 1800 |
| Host | Name server | TTL |
|---|---|---|
| gomsajang.com | dns1.cafe24.co.kr | 1800 |
| gomsajang.com | dns1.cafe24.com | 1800 |
| gomsajang.com | dns2.cafe24.co.kr | 1800 |
| gomsajang.com | dns2.cafe24.com | 1800 |
| Host | Start of authority | TTL |
|---|---|---|
| gomsajang.com | gomsajang.com postmaster.gomsajang.com 20250502 10800 3600 3600000 43200 | 1800 |
Other domains served from 203.245.12.122. Normal for shared hosting and CDNs.
No reviews yet. Used gomsajang.com? 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.
gomsajang.com has no community safety rating yet. Its SSL certificate expired on 14 Mar 2026. See Security →
gomsajang.com is served from 4 IP addresses, mainly on AS4766 Korea Telecom in Korea (the Republic of). See Hosting →
The first response from http://www.gomsajang.com, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with gomsajang.com. 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.