4444.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 4444.jp. Refresh the analysis to check again.
Internet standards that make a site faster and safer.
656 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| 4444.fun | Other extension | 30 Oct 2026 | Active website | Report → |
| 4444.cash | Other extension | 22 Oct 2026 | Active website | Report → |
| 4444.finance | Other extension | 21 Oct 2026 | Active website | Report → |
| 4444.fund | Other extension | 21 Oct 2026 | Active website | Report → |
| 4444.vin | Other extension | 21 Oct 2026 | RedirectsRedirects to yulekefu.online | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is 4444.jp’s name taken on other extensions?
| Host | Mail server | TTL |
|---|---|---|
| 4444.jp | 1 aspmx.l.google.com | 3600 |
| 4444.jp | 5 alt1.aspmx.l.google.com | 3600 |
| 4444.jp | 5 alt2.aspmx.l.google.com | 3600 |
| 4444.jp | 10 aspmx2.googlemail.com | 3600 |
| 4444.jp | 10 aspmx3.googlemail.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| 4444.jp | 01.dnsv.jp | 86400 |
| 4444.jp | 02.dnsv.jp | 86400 |
| 4444.jp | 03.dnsv.jp | 86400 |
| 4444.jp | 04.dnsv.jp | 86400 |
| Host | Text | TTL |
|---|---|---|
| 4444.jp | "google-site-verification=TWJo3c4QPgGxdB99kB9U93Z469WRUu5E9-06g7hyWtw" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| 4444.jp | 01.dnsv.jp hostmaster.dnsv.jp 1672500096 3600 900 604800 300 | 86400 |
No reviews yet. Used 4444.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.
4444.jp has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
4444.jp is registered through whois.jprs.jp. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
Raw registry data for 4444.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] 4444.JP
[登録者名] （登録者からの申請により非表示）
詳細は→https://jprs.jp/about/dom-rule/whois-concealment/
[Registrant] (Not displayed by registrant's request)
For details -> https://jprs.jp/about/dom-rule/whois-concealment/ (only in Japanese)
[Name Server] 01.dnsv.jp
[Name Server] 02.dnsv.jp
[Name Server] 03.dnsv.jp
[Name Server] 04.dnsv.jp
[Signing Key]
[登録年月日] 2017/06/01
[有効期限] 2027/06/30
[状態] Active
[最終更新] 2026/07/01 01:05:03 (JST)
Contact Information: [公開連絡窓口]
[名前] Whois情報公開代行サービス by お名前.com
[Name] Whois Privacy Protection Service by onamae.com
[Email] [email protected]
[Web Page]
[郵便番号] 150-8512
[住所] 東京都渋谷区
桜丘町 26-1
セルリアンタワー 11階
[Postal Address] Shibuya-ku
26-1 Sakuragaoka-cho
Cerulean Tower 11F
[電話番号] +81.354562560
[FAX番号]Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with 4444.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 30 Oct 2026.