gitlab.kaonavi.jp is registered with whois.jprs.jp. We couldn't read an SSL certificate for it when we last analysed it.
What security vendors and the WOT community say about this domain.
0 of 5 protections set up
No SPF record: any server can send mail that claims to come from this domain.
—No key at the 12 common selectors we checked. A custom selector can’t be found from DNS alone.
—No DMARC policy: receivers aren’t told what to do with mail that fails SPF and DKIM.
—Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
We couldn't read an SSL certificate on port 443 when we last analysed gitlab.kaonavi.jp. Refresh the analysis to check again.
Internet standards that make a site faster and safer.
2 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| kaenavi.com | Typo | 7 Aug 2026 | Checking… | Report → |
| katonavi.com | Extra letter | 15 Sept 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is gitlab.kaonavi.jp’s name taken on other extensions?
| Host | IPv4 address | TTL |
|---|---|---|
| gitlab.kaonavi.jp | 10.30.1.190 | 60 |
No reviews yet. Used gitlab.kaonavi.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.
gitlab.kaonavi.jp has no community safety rating yet, and it isn't on any of the 6 blocklists we check. We couldn't read an SSL certificate on it when we last analysed it. See Security →
gitlab.kaonavi.jp is registered through whois.jprs.jp. See WHOIS →
Raw registry data for gitlab.kaonavi.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'. ]
No match!!
JPRS WHOISは、JPRSが管理している以下のドメイン名に関する情報を確認でき
るサービスです。
・登録されているJPドメイン名
・JPRSを管理レジストラとするgTLD等ドメイン名
詳しくは https://jprs.jp/about/dom-search/jprs-whois/ を参照してください。
参考: IPアドレスのWHOISサーバ
・JPNIC WHOIS(whois.nic.ad.jp)
・APNIC WHOIS(whois.apnic.net)
・ARIN WHOIS(whois.arin.net)
・RIPE WHOIS(whois.ripe.net)
・LACNIC WHOIS(whois.lacnic.net)
・AfriNIC WHOIS(whois.afrinic.net)Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with gitlab.kaonavi.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.
0 of 6 blocklists list this domain's IP or mail servers.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 28 Oct 2026.
Found in public certificate transparency logs.
| Subdomain | First seen |
|---|---|
| kintai.kaonavi.jp | Sept 2026 |
| stg.kintai.kaonavi.jp | Sept 2026 |
| dev.portal-manager.kaonavi.jp | Apr 2026 |
| em.kaonavi.jp | Sept 2023 |
| service-secure.ecs-dev.kaonavi.jp | Sept 2026 |