saka.yokohama is registered with whois.nic.yokohama and is hosted on AS7506 Interq Gmo Internet Group Inc. in Japan. Its SSL certificate from Let's Encrypt expired on 3 Jul 2025.
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 saka.yokohama’s name taken on other extensions?
Every IP address saka.yokohama resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| saka.yokohama | 163.44.185.192 | 3600 |
| Host | Mail server | TTL |
|---|---|---|
| saka.yokohama | 50 mx01.lolipop.jp | 3600 |
| Host | Name server | TTL |
|---|---|---|
| saka.yokohama | dns01.muumuu-domain.com | 3600 |
| saka.yokohama | dns02.muumuu-domain.com | 3600 |
| Host | Text | TTL |
|---|---|---|
| saka.yokohama | "v=spf1 include:_spf.lolipop.jp ~all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| saka.yokohama | dns01.muumuu-domain.com postmaster.saka.yokohama 1713403400 3600 1800 604800 3600 | 3600 |
Other domains served from 163.44.185.192. Normal for shared hosting and CDNs.
No reviews yet. Used saka.yokohama? 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.
saka.yokohama has no community safety rating yet. Its SSL certificate expired on 3 Jul 2025. See Security →
saka.yokohama is registered through whois.nic.yokohama. See WHOIS →
saka.yokohama is served from 1 IP address, mainly on AS7506 Interq Gmo Internet Group Inc. in Japan. See Hosting →
Raw registry data for saka.yokohama. May be redacted by privacy services.
Server is busy now, please try again later.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with saka.yokohama. 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.