svd.expert was registered on 16 Jan 2014. 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 svd.expert. Refresh the analysis to check again.
Internet standards that make a site faster and safer.
574 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| svcl.co.uk | Look-alike characters | 20 Oct 2026 | Checking… | Report → |
| sdv.wine | Typo | 15 Nov 2026 | Checking… | Report → |
| svd.fyi | Other extension | 15 Nov 2026 | Checking… | Report → |
| vsd.com.br | Typo | 8 Nov 2026 | Checking… | Report → |
| vsd.lat | Typo | 4 Nov 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is svd.expert’s name taken on other extensions?
No reviews yet. Used svd.expert? 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.
svd.expert has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
svd.expert was registered on 16 Jan 2014, making it 12 years old. See Overview →
Raw registry data for svd.expert. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: domain: EXPERT organisation: Binky Moon, LLC address: c/o Identity Digital Inc. address: 10500 NE 8th Street, Suite 750 address: Bellevue WA 98004 address: United States of America (the) contact: administrative name: Vice President, Engineering organisation: Identity Digital Inc. address: 10500 NE 8th Street, Suite 750 address: Bellevue WA 98004 address: United States of America (the) phone: +1.425.298.2200 fax-no: +1.425.671.0020 e-mail: tldadmin@identity.digital contact: technical name: Senior Director, DNS Infrastructure Group organisation: Identity Digital Limited address: c/o Identity Digital Inc. address: 10500 NE 8th Street, Suite 750 address: Bellevue WA 98004 address: United States of America (the) phone: +1.425.298.2200 fax-no: +1.425.671.0020 e-mail: tldtech@identity.digital nserver: V0N0.NIC.EXPERT 2a01:8840:22:0:0:0:0:4 65.22.32.4 nserver: V0N1.NIC.EXPERT 2a01:8840:23:0:0:0:0:4 65.22.33.4 nserver: V0N2.NIC.EXPERT 2a01:8840:24:0:0:0:0:4 65.22.34.4 nserver: V0N3.NIC.EXPERT 161.232.16.4 2a01:8840:fa:0:0:0:0:4 nserver: V2N0.NIC.EXPERT 2a01:8840:25:0:0:0:0:4 65.22.35.4 nserver: V2N1.NIC.EXPERT 161.232.17.4 2a01:8840:fb:0:0:0:0:4 ds-rdata: 35986 8 2 8bb05a08616e1d432c7118d31fca1c48e3cfaa536dc81fac428eb3a4d695153c ds-rdata: 41596 8 2 4dad4ac4d232bf3fc10d0d2a0fdd814776e826781a88099cf5ad5edbe6ffd76f whois: status: ACTIVE remarks: Registration information: https://www.identity.digital/ created: 2014-01-16 changed: 2026-10-27 source: IANA
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with svd.expert. 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.
We couldn't find an IP address for svd.expert's web or mail servers to check.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 1 Nov 2026.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.