snft.jp is registered with whois.jprs.jp and is hosted on AS16509 Amazon.com Inc. in United States of America. Its SSL certificate from Let's Encrypt is valid until 2 Jan 2027.
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.
228 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| snft.site | Other extension | 24 Oct 2026 | RedirectsRedirects to expireddomains.com | Report → |
| sntf.us | Typo | 20 Oct 2026 | RedirectsRedirects to iptv-belgie.eu | Report → |
| snft.store | Other extension | 10 Sept 2026 | No website | Report → |
| snft.dev | Other extension | 9 Sept 2026 | No website | Report → |
| snft.fun | Other extension | 8 Sept 2026 | Active website | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is snft.jp’s name taken on other extensions?
Every IP address snft.jp resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| snft.jp | 76.76.21.21 | 300 |
| Host | Name server | TTL |
|---|---|---|
| snft.jp | ns-1008.awsdns-62.net | 172800 |
| snft.jp | ns-1481.awsdns-57.org | 172800 |
| snft.jp | ns-1969.awsdns-54.co.uk | 172800 |
| snft.jp | ns-33.awsdns-04.com | 172800 |
| Host | Text | TTL |
|---|---|---|
| snft.jp | "e0b7ae8c-e9c8-4c36-bf65-45ea9db1e2a2=a5d10b29b42781bb0ec1193ec8d0da8e99a3f9e6c6da75d350755d6fe23ba42f" | 600 |
| Host | Start of authority | TTL |
|---|---|---|
| snft.jp | ns-1969.awsdns-54.co.uk awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
Other domains served from 76.76.21.21. Normal for shared hosting and CDNs.
No reviews yet. Used snft.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.
snft.jp has no community safety rating yet. Its SSL certificate is valid until 2 Jan 2027. See Security →
snft.jp is registered through whois.jprs.jp. See WHOIS →
snft.jp is served from 1 IP address, mainly on AS16509 Amazon.com Inc. in United States of America. See Hosting →
Raw registry data for snft.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] SNFT.JP [登録者名] SNFT Inc. [Registrant] SNFT Inc. [Name Server] ns-1481.awsdns-57.org [Name Server] ns-1969.awsdns-54.co.uk [Name Server] ns-33.awsdns-04.com [Name Server] ns-1008.awsdns-62.net [Signing Key] [登録年月日] 2021/12/24 [有効期限] 2026/12/31 [状態] Active [最終更新] 2026/04/01 18:27:07 (JST) Contact Information: [公開連絡窓口] [名前] Daisuke Matsuzawa [Name] Daisuke Matsuzawa [Email] [email protected] [Web Page] [郵便番号] 108-0075 [住所] 東京都1-7-1 Konan Minato-ku [Postal Address] [電話番号] +81.5038507229 [FAX番号]
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with snft.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.