Alternatives to longdo.com
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
longdo.com was registered with whois.verisign-grs.com on 5 Jun 2002 and is hosted on AS9335 CAT Telecom Public Company Limited in Thailand. Its SSL certificate from DigiCert Inc expired on 20 Sept 2024, and the site does not support HTTP/3. WOT's community rates its safety good (63/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.
147 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| longdo.me | Other extension | 5 Oct 2026 | Checking… | Report → |
| longdi.site | Typo | 14 Nov 2026 | Checking… | Report → |
| lingdo.top | Typo | 25 Oct 2026 | Checking… | Report → |
| lingdo.studio | Typo | 28 Sept 2026 | Checking… | Report → |
| londo.me | Typo | 8 Nov 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is longdo.com’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Thailand | 88.4% | 5,213,737 | 36.1% | 63.9% |
| Germany | 3.2% | 188,498 | 0.9% | 99.1% |
| France | 2.9% | 171,967 | 0% | 100% |
| United States | 1.2% | 69,556 | 72.5% | 27.5% |
| Russia | 0.7% | 38,087 | 0% | 100% |
Every IP address longdo.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| longdo.com | 122.155.165.32 | 21600 |
| Host | Mail server | TTL |
|---|---|---|
| longdo.com | 1 aspmx.l.google.com | 3600 |
| longdo.com | 5 alt1.aspmx.l.google.com | 3600 |
| longdo.com | 5 alt2.aspmx.l.google.com | 3600 |
| longdo.com | 10 aspmx2.googlemail.com | 3600 |
| longdo.com | 10 aspmx3.googlemail.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| longdo.com | ns77.worldnic.com | 7200 |
| longdo.com | ns78.worldnic.com | 7200 |
| Host | Text | TTL |
|---|---|---|
| longdo.com | "google-site-verification=_701fPKw-t3gGW5UMeUxiN81UdEz0pJ6jpFf7TWIv8M" | 21600 |
| longdo.com | "MS=A22D723C9AA640C3D536703C2D25F2FB8FDE6049" | 3600 |
| longdo.com | "v=spf1 ip4:122.155.165.31 ip4:122.155.165.32 ip4:122.155.165.49 include:_spf.google.com include:sendgrid.net ~all" | 21600 |
| Host | Start of authority | TTL |
|---|---|---|
| longdo.com | NS77.WORLDNIC.com namehost.WORLDNIC.com 123092804 10800 3600 604800 3600 | 7200 |
Other domains served from 122.155.165.32. Normal for shared hosting and CDNs.
No reviews yet. Used longdo.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 longdo.com good for safety (63/100). Its SSL certificate expired on 20 Sept 2024. See Security →
longdo.com is registered through whois.verisign-grs.com. See WHOIS →
The registration expires on 5 Jun 2028 — in 18 months. See Overview →
longdo.com was registered on 5 Jun 2002, making it 24 years old. See Overview →
longdo.com is served from 1 IP address, mainly on AS9335 CAT Telecom Public Company Limited in Thailand. See Hosting →
Raw registry data for longdo.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"87276856_DOMAIN_COM-VRSN","ldhName":"LONGDO.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/LONGDO.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/LONGDO.COM","type":"application\/rdap+json"},{"value":"https:\/\/rdap.networksolutions.com\/rdap\/domain\/LONGDO.COM","rel":"related","href":"https:\/\/rdap.networksolutions.com\/rdap\/domain\/LONGDO.COM","type":"application\/rdap+json"}],"status":["client transfer prohibited"],"entities":[{"objectClassName":"entity","handle":"2","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"2"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","Network Solutions, LLC"]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+1.8777228662"],["email",{},"text","domain.operations@web.com"]]]}]}],"events":[{"eventAction":"registration","eventDate":"2002-06-05T22:29:52Z"},{"eventAction":"expiration","eventDate":"2028-06-05T22:29:52Z"},{"eventAction":"last changed","eventDate":"2023-02-24T02:38:52Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-10-24T21:30:28Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"NS77.WORLDNIC.COM"},{"objectClassName":"nameserver","ldhName":"NS78.WORLDNIC.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.longdo.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 longdo.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.