microtouch.ltd was registered on 6 Aug 2015 and is hosted on AS45102 in Hong Kong. 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 microtouch.ltd. Refresh the analysis to check again.
Internet standards that make a site faster and safer.
Is microtouch.ltd’s name taken on other extensions?
Every IP address microtouch.ltd resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| expired.hichina.com | 47.76.127.217 | 600 |
| expired.hichina.com | 47.91.170.222 | 600 |
| expired.hichina.com | 8.218.208.240 | 600 |
| Host | Name server | TTL |
|---|---|---|
| microtouch.ltd | dns25.hichina.com | 86400 |
| microtouch.ltd | dns26.hichina.com | 86400 |
| Host | Start of authority | TTL |
|---|---|---|
| microtouch.ltd | dns25.hichina.com hostmaster.hichina.com 2020093003 3600 1200 86400 600 | 600 |
Other domains served from 47.76.127.217. Normal for shared hosting and CDNs.
No reviews yet. Used microtouch.ltd? 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.
microtouch.ltd has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
microtouch.ltd was registered on 6 Aug 2015, making it 11 years old. See Overview →
microtouch.ltd is served from 3 IP addresses, mainly on AS45102 in Hong Kong. See Hosting →
Raw registry data for microtouch.ltd. 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: LTD 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: [email protected] 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: [email protected] nserver: V0N0.NIC.LTD 2a01:8840:1e:0:0:0:0:2 65.22.28.2 nserver: V0N1.NIC.LTD 2a01:8840:1f:0:0:0:0:2 65.22.29.2 nserver: V0N2.NIC.LTD 2a01:8840:20:0:0:0:0:2 65.22.30.2 nserver: V0N3.NIC.LTD 161.232.14.2 2a01:8840:f8:0:0:0:0:2 nserver: V2N0.NIC.LTD 2a01:8840:21:0:0:0:0:2 65.22.31.2 nserver: V2N1.NIC.LTD 161.232.15.2 2a01:8840:f9:0:0:0:0:2 ds-rdata: 54 8 2 d0f5f5a210d27f70a8912bf81078beeb34dbd370d7f0470d1140b749ac2f3a46 whois: status: ACTIVE remarks: Registration information: https://www.identity.digital/ created: 2015-08-06 changed: 2025-10-07 source: IANA
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with microtouch.ltd. 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.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 19 Oct 2026.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.