recruit.co.jp is registered with whois.jprs.jp and is hosted on AS16509 Amazon.com Inc. in Japan. Its SSL certificate from Amazon expired on 1 Nov 2024, and the site does not support HTTP/3. WOT's community rates its safety excellent (80/100).
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 recruit.co.jp’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Japan | 99.2% | 32,098,225 | 13.1% | 86.9% |
| Taiwan | 0.2% | 77,969 | 14.8% | 85.2% |
| United States | 0.2% | 47,517 | 60.5% | 39.5% |
| France | 0.1% | 21,033 | 6.4% | 93.6% |
| Canada | 0.1% | 18,373 | 20% | 80% |
2 technologies detected across 2 categories.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address recruit.co.jp resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| recruit.co.jp | 18.176.127.94 | 300 |
| Host | Mail server | TTL |
|---|---|---|
| recruit.co.jp | 10 mx.x.recruit.co.jp | 300 |
| Host | Name server | TTL |
|---|---|---|
| recruit.co.jp | ns010-0vq2ghgrtbev88gb.0.d-53.info | 300 |
| recruit.co.jp | ns010-0vq2ghgrtbev88gb.0.d-53.jp | 300 |
| recruit.co.jp | ns010-0vq2ghgrtbev88gb.0.d-53.net | 300 |
| recruit.co.jp | ns1.x.recruit.co.jp | 300 |
| recruit.co.jp | ns2.x.recruit.co.jp | 300 |
| recruit.co.jp | ns3.x.recruit.co.jp | 300 |
| Host | Text | TTL |
|---|---|---|
| recruit.co.jp | "globalsign-domain-verification=B2hA2VWDR-7uiBHzi9PTRVB0VgzyYzHR3vIQ4oPRvy" | 300 |
| recruit.co.jp | "google-site-verification=tLjxepwzzNLaUtIjsQw5nYeHcLOfBDfZVcWRLr7vwUo" | 300 |
| recruit.co.jp | "v=spf1 include:spf01.isize.com include:spf02.isize.com include:spf-bma.rec.mpme.jp include:spf.tricorn.net ~all" | 300 |
| Host | Start of authority | TTL |
|---|---|---|
| recruit.co.jp | ns1.x.recruit.co.jp postmaster.x.recruit.co.jp 2024011901 3600 900 604800 3600 | 300 |
No reviews yet. Used recruit.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.
WOT's community rates recruit.co.jp excellent for safety (80/100). Its SSL certificate expired on 1 Nov 2024. See Security →
recruit.co.jp is registered through whois.jprs.jp. See WHOIS →
recruit.co.jp is served from 1 IP address, mainly on AS16509 Amazon.com Inc. in Japan. See Hosting →
We detected 2 technologies, including Google Analytics and jQuery. See Built with →
Raw registry data for recruit.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. [ドメイン名] RECRUIT.CO.JP e. [そしきめい] かぶしきがいしゃりくるーと f. [組織名] 株式会社リクルート g. [Organization] RECRUIT CO., LTD. k. [組織種別] 株式会社 l. [Organization Type] Company m. [登録担当者] YK56362JP n. [技術連絡担当者] YK32084JP p. [ネームサーバ] ns1.x.recruit.co.jp p. [ネームサーバ] ns2.x.recruit.co.jp p. [ネームサーバ] ns3.x.recruit.co.jp p. [ネームサーバ] ns010-0vq2ghgrtbev88gb.0.d-53.jp p. [ネームサーバ] ns010-0vq2ghgrtbev88gb.0.d-53.net p. [ネームサーバ] ns010-0vq2ghgrtbev88gb.0.d-53.info s. [署名鍵] [状態] Connected (2024/11/30) [登録年月日] 2017/11/13 [接続年月日] 2017/11/13 [最終更新] 2023/12/01 01:01:18 (JST)
The first response from http://www.recruit.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 recruit.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.
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.