sumo.fans was registered with whois.nic.fans on 5 Feb 2015. 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 sumo.fans. Refresh the analysis to check again.
Internet standards that make a site faster and safer.
442 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| 5umo.com | Look-alike characters | 7 Oct 2026 | No website | Report → |
| sumo.id | Other extension | 19 Oct 2026 | No website | Report → |
| sumo.lt | Other extension | 19 Oct 2026 | No website | Report → |
| sumo.uk.com | Other extension | 5 Oct 2026 | No website | Report → |
| suom.io | Typo | 5 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is sumo.fans’s name taken on other extensions?
| Host | Name server | TTL |
|---|---|---|
| sumo.fans | ns-1368.awsdns-43.org | 172800 |
| sumo.fans | ns-1642.awsdns-13.co.uk | 172800 |
| sumo.fans | ns-210.awsdns-26.com | 172800 |
| sumo.fans | ns-619.awsdns-13.net | 172800 |
| Host | Start of authority | TTL |
|---|---|---|
| sumo.fans | ns-210.awsdns-26.com awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
No reviews yet. Used sumo.fans? 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.
sumo.fans has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
sumo.fans is registered through whois.nic.fans. See WHOIS →
sumo.fans was registered on 5 Feb 2015, making it 11 years old. See Overview →
Raw registry data for sumo.fans. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object domain: FANS organisation: ZDNS International Limited address: 4, South 4th Street, Zhongguancun address: Haidian District address: Beijing 100190 address: China contact: administrative name: Vice President organisation: ZDNS address: 4, South 4th Street, Zhongguancun address: Haidian District address: Beijing 100190 address: China phone: +86.1058812426 e-mail: [email protected] contact: technical name: CTO organisation: CentralNic address: Saddlers House, 4th Floor address: 44 Gutter Lane address: London EC2V 6BR address: United Kingdom of Great Britain and Northern Ireland (the) phone: +44 20 33 88 0600 fax-no: +44 20 33 88 0601 e-mail: [email protected] nserver: A.NIC.FANS 194.169.218.39 2001:67c:13cc:0:0:0:1:39 nserver: B.NIC.FANS 185.24.64.39 2a04:2b00:13cc:0:0:0:1:39 nserver: C.NIC.FANS 212.18.248.39 2a04:2b00:13ee:0:0:0:0:39 nserver: D.NIC.FANS 212.18.249.39 2a04:2b00:13ff:0:0:0:0:39 ds-rdata: 25466 8 2 7842246f760a21e694f1d8b64754f0d5bb27ef6a33f25e2f3f2dee26b33b118b ds-rdata: 46294 8 2 c84814f11abfa3a32c3403cd3072afe0cc289e7c2fd92b25ef789778e491d680 whois: whois.nic.fans status: ACTIVE remarks: Registration information: http://www.nic.fans/ created: 2015-02-05 changed: 2026-10-30 source: IANA
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with sumo.fans. 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 8 Nov 2026.