0081.jp is registered with whois.jprs.jp and is hosted on AS7506 in Japan. 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 0081.jp. Refresh the analysis to check again.
Internet standards that make a site faster and safer.
The path from a typed address to the final page.
191 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| 008l.cn | Look-alike characters | 19 Sept 2026 | Checking… | Report → |
| 008i.vip | Look-alike characters | 23 Aug 2026 | Checking… | Report → |
| 0018.app | Typo | 8 Nov 2026 | Active website | Report → |
| 0018.my | Typo | 8 Nov 2026 | On a blocklistListed on Mailspike | Report → |
| 0081.bet | Other extension | 31 Oct 2026 | Parked | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is 0081.jp’s name taken on other extensions?
Every IP address 0081.jp resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| 0081.jp | 118.27.125.171 | 3600 |
| Host | Mail server | TTL |
|---|---|---|
| 0081.jp | 50 mx01.lolipop.jp | 3600 |
| Host | Name server | TTL |
|---|---|---|
| 0081.jp | dns01.muumuu-domain.com | 3600 |
| 0081.jp | dns02.muumuu-domain.com | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| 0081.jp | dns01.muumuu-domain.com postmaster.0081.jp 1700899030 3600 1800 604800 3600 | 3600 |
Other domains served from 118.27.125.171. Normal for shared hosting and CDNs.
No reviews yet. Used 0081.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.
0081.jp has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
0081.jp is registered through whois.jprs.jp. See WHOIS →
0081.jp is served from 1 IP address, mainly on AS7506 in Japan. See Hosting →
Raw registry data for 0081.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] 0081.JP
[登録者名] 鄭 則栄
[Registrant] NORIYOSHI TEI
[Name Server] dns01.muumuu-domain.com
[Name Server] dns02.muumuu-domain.com
[Signing Key]
[登録年月日] 2023/01/15
[有効期限] 2027/01/31
[状態] Active
[最終更新] 2026/03/31 16:45:26 (JST)
Contact Information: [公開連絡窓口]
[名前] [代理公開情報]GMOペパボ株式会社
[Name] GMO Pepabo, Inc.
[Email] admin@muumuu-domain.com
[Web Page] http://muumuu-domain.com/?mode=whois-policy
[郵便番号] 810-0001
[住所] 福岡県福岡市中央区
天神2丁目8−35
天神住友生命FJビジネスセンター22F
[Postal Address] 22F Tenjin Sumitomo Life FJ Business Center
2-8-35 Tenjin
Chuo-ku,Fukuoka-City,Fukuoka,8100001,Jpan
[電話番号] 092-713-7999
[FAX番号] 092-713-7944The first response from http://www.0081.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 0081.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 20 Nov 2026.