Alternatives to nippon.com
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
nippon.com was registered with whois.verisign-grs.com on 14 Feb 1992 and is hosted on AS16509 Amazon.com Inc. in Japan. Its SSL certificate from "SECOM Trust Systems CO. expired on 10 Nov 2024, and the site does not support HTTP/3. WOT's community rates its safety good (75/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.
329 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| nippon.golf | Other extension | 23 Oct 2026 | Checking… | Report → |
| nippon.ninja | Other extension | 15 Oct 2026 | Checking… | Report → |
| nippon.fun | Other extension | 4 Oct 2026 | Checking… | Report → |
| nippon.gold | Other extension | 27 Sept 2026 | Checking… | Report → |
| nippon.nu | Other extension | 27 Sept 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is nippon.com’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Japan | 52.1% | 1,854,680 | 24.2% | 75.9% |
| Taiwan | 9.9% | 353,491 | 13.2% | 86.8% |
| United States | 5.4% | 192,404 | 39% | 61% |
| France | 4.2% | 149,218 | 7.8% | 92.2% |
| Norway | 4% | 142,305 | 1.5% | 98.5% |
Every IP address nippon.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| nippon.com | 18.65.185.84 | 300 |
| Host | Mail server | TTL |
|---|---|---|
| nippon.com | 1 aspmx.l.google.com | 3600 |
| nippon.com | 5 alt1.aspmx.l.google.com | 3600 |
| nippon.com | 5 alt2.aspmx.l.google.com | 3600 |
| nippon.com | 10 alt3.aspmx.l.google.com | 3600 |
| nippon.com | 10 alt4.aspmx.l.google.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| nippon.com | 01.dnsv.jp | 21600 |
| nippon.com | 02.dnsv.jp | 21600 |
| nippon.com | 03.dnsv.jp | 21600 |
| nippon.com | 04.dnsv.jp | 21600 |
| Host | Text | TTL |
|---|---|---|
| nippon.com | "apple-domain-verification=rrN7HXozHRDHJpO6" | 3600 |
| nippon.com | "v=spf1 include:_spf.google.com ~all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| nippon.com | 01.dnsv.jp hostmaster.dnsv.jp 1698209131 3600 900 604800 300 | 21600 |
No reviews yet. Used nippon.com? 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 nippon.com good for safety (75/100). Its SSL certificate expired on 10 Nov 2024. See Security →
nippon.com is registered through whois.verisign-grs.com. See WHOIS →
The registration expired on 15 Feb 2024. See Overview →
nippon.com was registered on 14 Feb 1992, making it 34 years old. See Overview →
nippon.com is served from 1 IP address, mainly on AS16509 Amazon.com Inc. in Japan. See Hosting →
Raw registry data for nippon.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"438927_DOMAIN_COM-VRSN","ldhName":"NIPPON.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/NIPPON.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/NIPPON.COM","type":"application\/rdap+json"},{"value":"https:\/\/rdap.gmo-onamae.com\/rdap\/v1\/domain\/NIPPON.COM","rel":"related","href":"https:\/\/rdap.gmo-onamae.com\/rdap\/v1\/domain\/NIPPON.COM","type":"application\/rdap+json"}],"status":["active"],"entities":[{"objectClassName":"entity","handle":"49","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"49"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","GMO Internet Group, Inc. d\/b\/a Onamae.com"]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+81.337709199"],["email",{},"text","[email protected]"]]]}]}],"events":[{"eventAction":"registration","eventDate":"1992-02-14T05:00:00Z"},{"eventAction":"expiration","eventDate":"2024-02-15T05:00:00Z"},{"eventAction":"last changed","eventDate":"2023-06-14T00:10:29Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-10-27T08:38:32Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"01.DNSV.JP"},{"objectClassName":"nameserver","ldhName":"02.DNSV.JP"}],"rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_0","icann_rdap_response_profile_0"],"notices":[{"title":"Terms of Use","description":["Service subject to Terms of Use."],"links":[{"href":"https:\/\/www.verisign.com\/domain-names\/registration-data-access-protocol\/terms-service\/index.xhtml","type":"text\/html"}]},{"title":"Status Codes","description":["For more information on domain status codes, please visit https:\/\/icann.org\/epp"],"links":[{"href":"https:\/\/icann.org\/epp","type":"text\/html"}]},{"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https:\/\/icann.org\/wicf"],"links":[{"href":"https:\/\/icann.org\/wicf","type":"text\/html"}]}]}The first response from http://www.nippon.com, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with nippon.com. 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.
We record what changes from the next time this report is refreshed.