makuake.co.jp is registered with whois.jprs.jp and is hosted on AS16509 Amazon.com Inc. in India. Its SSL certificate from Amazon expired on 19 Jan 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 makuake.co.jp’s name taken on other extensions?
3 technologies detected across 3 categories.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address makuake.co.jp resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| makuake.co.jp | 18.66.78.25 | 60 |
| makuake.co.jp | 18.66.78.54 | 60 |
| makuake.co.jp | 18.66.78.67 | 60 |
| makuake.co.jp | 18.66.78.71 | 60 |
| Host | Mail server | TTL |
|---|---|---|
| makuake.co.jp | 1 aspmx.l.google.com | 300 |
| makuake.co.jp | 5 alt1.aspmx.l.google.com | 300 |
| makuake.co.jp | 5 alt2.aspmx.l.google.com | 300 |
| makuake.co.jp | 10 alt3.aspmx.l.google.com | 300 |
| makuake.co.jp | 10 alt4.aspmx.l.google.com | 300 |
| Host | Name server | TTL |
|---|---|---|
| makuake.co.jp | ns-1018.awsdns-63.net | 300 |
| makuake.co.jp | ns-1175.awsdns-18.org | 300 |
| makuake.co.jp | ns-1604.awsdns-08.co.uk | 300 |
| makuake.co.jp | ns-474.awsdns-59.com | 300 |
| Host | Text | TTL |
|---|---|---|
| makuake.co.jp | "google-site-verification=ClvM66e-RTj-IHk53wHXe-KQOCSFWIS5h_yOOOShjl8" | 60 |
| makuake.co.jp | "google-site-verification=PpK5-Uo-7eZ8_A5UC0P8bi4kPaG2HWeh0AUp9RDkc6Q" | 60 |
| makuake.co.jp | "MS=ms59142990" | 60 |
| makuake.co.jp | "v=spf1 ip4:210.190.116.0/25 ip4:133.217.192.19/32 ip4:133.217.192.20/32 ip4:133.217.192.21/32 ip4:133.217.192.22/32 " "include:_spf.google.com include:mail.zendesk.com include:webcas.net include:amazonses.com " "include:spf10.htdb.jp include:spf20.htdb.jp include:spf30.htdb.jp ~all" | 60 |
| Host | Start of authority | TTL |
|---|---|---|
| makuake.co.jp | ns-1175.awsdns-18.org awsdns-hostmaster.amazon.com 2 600 300 6000 300 | 300 |
Other domains served from 18.66.78.25. Normal for shared hosting and CDNs.
No reviews yet. Used makuake.co.jp? 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.
makuake.co.jp has no community safety rating yet. Its SSL certificate expired on 19 Jan 2025. See Security →
makuake.co.jp is registered through whois.jprs.jp. See WHOIS →
makuake.co.jp is served from 4 IP addresses, mainly on AS16509 Amazon.com Inc. in India. See Hosting →
We detected 3 technologies, including Google Analytics, WordPress and jQuery. See Built with →
Raw registry data for makuake.co.jp. May be redacted by privacy services.
[ JPRS database provides information on network administration. Its use is ] [ restricted to network administration purposes. For further information, ] [ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ] [ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ] Domain Information: [ドメイン情報] a. [ドメイン名] MAKUAKE.CO.JP e. [そしきめい] かぶしきがいしゃまくあけ f. [組織名] 株式会社マクアケ g. [Organization] Makuake, Inc. k. [組織種別] 株式会社 l. [Organization Type] corporation m. [登録担当者] MN35827JP n. [技術連絡担当者] HY4200JP p. [ネームサーバ] ns-1018.awsdns-63.net p. [ネームサーバ] ns-1175.awsdns-18.org p. [ネームサーバ] ns-1604.awsdns-08.co.uk p. [ネームサーバ] ns-474.awsdns-59.com s. [署名鍵] [状態] Connected (2024/09/30) [登録年月日] 2017/09/01 [接続年月日] 2017/09/01 [最終更新] 2023/10/01 01:06:29 (JST)
The first response from http://www.makuake.co.jp, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with makuake.co.jp. 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.