liaison.com was registered with whois.verisign-grs.com on 15 Oct 1997 and is hosted on AS16751 Open Text Corporation in Canada. Its SSL certificate from Sectigo Limited expired on 23 Aug 2024, and the site does not support HTTP/3. WOT's community rates its safety excellent (89/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.
323 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| liaison.casa | Other extension | 2 Oct 2026 | Checking… | Report → |
| liaison.work | Other extension | 10 Sept 2026 | Checking… | Report → |
| liaison.digital | Other extension | 8 Sept 2026 | Checking… | Report → |
| liaison.beauty | Other extension | 22 Aug 2026 | Checking… | Report → |
| liaison.events | Other extension | 6 Aug 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is liaison.com’s name taken on other extensions?
1 technology detected across 1 category.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address liaison.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| liaison.com | 205.211.178.124 | 300 |
| Host | Mail server | TTL |
|---|---|---|
| liaison.com | 10 mxa-00102601.gslb.pphosted.com | 300 |
| liaison.com | 10 mxb-00102601.gslb.pphosted.com | 300 |
| Host | Name server | TTL |
|---|---|---|
| liaison.com | ns1.opntxtdns.com | 900 |
| liaison.com | ns2.opntxtdns.com | 900 |
| liaison.com | ns4.opntxtdns.com | 900 |
| liaison.com | ns5.opntxtdns.com | 900 |
| Host | Text | TTL |
|---|---|---|
| liaison.com | "5a47d8989d434738aa3b544e8e7ed7e6" | 900 |
| liaison.com | "MS=ms28740434" | 900 |
| liaison.com | "ms=ms59604648" | 900 |
| liaison.com | "pardot463922=6eba0069022c18401274cbba1b57fcf557d5229dbe9bf09c58e1f5c918efc758" | 900 |
| liaison.com | "pmvw8dbB0B7ntjwgOMkYkzdcGCPC68cJVeEIMj5jB4s0ruQte6/lb316xnnLutGjIPcswR5wxWXNybtyKGU5UA==" | 900 |
| liaison.com | "postman-domain-verification=81678b88f09e41e0562e63a42af8b9709f9592bf73c27c01f741a9d44aa6b4ab" | 900 |
| liaison.com | "status-page-domain-verification=xl2v97y71f9k" | 900 |
| liaison.com | "v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all" | 900 |
| Host | Start of authority | TTL |
|---|---|---|
| liaison.com | ns1.opntxtdns.com dnsnotifications.liaison.com 2019072144 3600 1800 2419200 60 | 900 |
Other domains served from 205.211.178.124. Normal for shared hosting and CDNs.
No reviews yet. Used liaison.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 liaison.com excellent for safety (89/100). Its SSL certificate expired on 23 Aug 2024. See Security →
liaison.com is registered through whois.verisign-grs.com. See WHOIS →
The registration expired on 14 Oct 2024. See Overview →
liaison.com was registered on 15 Oct 1997, making it 29 years old. See Overview →
liaison.com is served from 1 IP address, mainly on AS16751 Open Text Corporation in Canada. See Hosting →
We detected 1 technology, including jQuery UI. See Built with →
Raw registry data for liaison.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"3228199_DOMAIN_COM-VRSN","ldhName":"LIAISON.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/LIAISON.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/LIAISON.COM","type":"application\/rdap+json"},{"value":"https:\/\/rdap.safenames.legal\/rdap\/domain\/LIAISON.COM","rel":"related","href":"https:\/\/rdap.safenames.legal\/rdap\/domain\/LIAISON.COM","type":"application\/rdap+json"}],"status":["client delete prohibited","client transfer prohibited","client update prohibited"],"entities":[{"objectClassName":"entity","handle":"447","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"447"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","SafeNames Ltd."]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+44.1908200022"],["email",{},"text","[email protected]"]]]}]}],"events":[{"eventAction":"registration","eventDate":"1997-10-15T04:00:00Z"},{"eventAction":"expiration","eventDate":"2024-10-14T04:00:00Z"},{"eventAction":"last changed","eventDate":"2023-10-14T23:53:51Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-10-24T14:37:34Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"NS1.OPNTXTDNS.COM"},{"objectClassName":"nameserver","ldhName":"NS2.OPNTXTDNS.COM"},{"objectClassName":"nameserver","ldhName":"NS4.OPNTXTDNS.COM"},{"objectClassName":"nameserver","ldhName":"NS5.OPNTXTDNS.COM"}],"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.liaison.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 liaison.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.