168.jp is registered with whois.jprs.jp and is hosted on AS9370 in Japan. Its SSL certificate doesn't cover this domain name, so browsers warn visitors.
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.
Internet standards that make a site faster and safer.
The path from a typed address to the final page.
680 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| l68.online | Look-alike characters | 28 Oct 2026 | Active website | Report → |
| l68.cam | Look-alike characters | 20 Oct 2026 | Active website | Report → |
| l68.lat | Look-alike characters | 18 Oct 2026 | Active website | Report → |
| i68.com.tw | Look-alike characters | 5 Oct 2026 | RedirectsRedirects to gobyexample.everyx.in | Report → |
| l68.bio | Look-alike characters | 11 Sept 2026 | Active website | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is 168.jp’s name taken on other extensions?
Every IP address 168.jp resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| 168.jp | 202.181.99.41 | 3600 |
| Host | Mail server | TTL |
|---|---|---|
| 168.jp | 10 168.jp | 3600 |
| Host | Name server | TTL |
|---|---|---|
| 168.jp | ns1.dns.ne.jp | 3600 |
| 168.jp | ns2.dns.ne.jp | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| 168.jp | master.dns.ne.jp tech.sakura.ad.jp 2024091801 3600 900 3600000 3600 | 3600 |
Other domains served from 202.181.99.41. Normal for shared hosting and CDNs.
No reviews yet. Used 168.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.
168.jp has no community safety rating yet. Its SSL certificate doesn't cover this domain name, so browsers warn visitors. See Security →
168.jp is registered through whois.jprs.jp. See WHOIS →
168.jp is served from 1 IP address, mainly on AS9370 in Japan. See Hosting →
Raw registry data for 168.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: [ドメイン情報] [Domain Name] 168.JP [登録者名] 森岡 和彦 [Registrant] morioka kazuhiko [Name Server] ns1.dns.ne.jp [Name Server] ns2.dns.ne.jp [Signing Key] [登録年月日] 2018/09/01 [有効期限] 2027/09/30 [状態] Active [最終更新] 2026/10/01 01:05:04 (JST) Contact Information: [公開連絡窓口] [名前] さくらインターネット株式会社 [Name] SAKURA internet Inc. [Email] [email protected] [Web Page] [郵便番号] 530-0011 [住所] 大阪府大阪市 北区大深町6番38号 グラングリーン大阪 北館 JAM BASE 3階 [Postal Address] Osaka Osaka GRAND GREEN OSAKA North, JAM BASE, 3F 6-38 Ofukacho, Kita-ku [電話番号] 06-6476-8790 [FAX番号]
The first response from http://www.168.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 168.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.
No changes seen since we started recording on 7 Nov 2026.