time.ly was registered with Libyan Spider Network (int) on 1 Mar 2009 and is hosted on AS16509 Amazon.com Inc. in Germany. Its SSL certificate from Amazon expired on 17 Oct 2024, and the site does not support HTTP/3.
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.
531 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| tim3.ru | Look-alike characters | 17 Oct 2026 | Checking… | Report → |
| tim3.my | Look-alike characters | 17 Sept 2026 | Checking… | Report → |
| tim3.xyz | Look-alike characters | 4 Sept 2026 | Checking… | Report → |
| time.info.pl | Other extension | 29 Oct 2026 | Checking… | Report → |
| time.barcelona | Other extension | 24 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is time.ly’s name taken on other extensions?
Every IP address time.ly resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| time.ly | 13.32.121.44 | 60 |
| time.ly | 13.32.121.86 | 60 |
| time.ly | 13.32.121.98 | 60 |
| time.ly | 13.32.121.99 | 60 |
| Host | Mail server | TTL |
|---|---|---|
| time.ly | 1 aspmx.l.google.com | 21600 |
| time.ly | 5 alt1.aspmx.l.google.com | 21600 |
| time.ly | 5 alt2.aspmx.l.google.com | 21600 |
| time.ly | 10 alt3.aspmx.l.google.com | 21600 |
| time.ly | 10 alt4.aspmx.l.google.com | 21600 |
| Host | Name server | TTL |
|---|---|---|
| time.ly | ns-1252.awsdns-28.org | 21600 |
| time.ly | ns-1820.awsdns-35.co.uk | 21600 |
| time.ly | ns-261.awsdns-32.com | 21600 |
| time.ly | ns-892.awsdns-47.net | 21600 |
| Host | Text | TTL |
|---|---|---|
| time.ly | "google-site-verification=UM3BXAYEmhUSPYha4JzdTHeyqtuabh8pqlWULN216Vg" | 300 |
| time.ly | "google-site-verification=V7GSXh3ETg2B11bXBaVddbB570ieYBCgLJmdZIdJ4kg" | 300 |
| time.ly | "MS=5848C8DDFFAD40EA3EC503120CD30058B3A79497" | 300 |
| time.ly | "v=spf1 include:amazonses.com include:_spf.google.com include:zcsend.net include:3832990.spf02.hubspotemail.net ~all" | 300 |
| Host | Policy | TTL |
|---|---|---|
| time.ly | 0 issue \; | 300 |
| time.ly | 0 issue amazon.com | 300 |
| time.ly | 0 issue amazonaws.com | 300 |
| time.ly | 0 issue amazontrust.com | 300 |
| time.ly | 0 issue awstrust.com | 300 |
| time.ly | 0 issue certsign.ro | 300 |
| time.ly | 0 issue digicert.com | 300 |
| time.ly | 0 issue docusign.fr | 300 |
| time.ly | 0 issue letsencrypt.org | 300 |
| time.ly | 0 issue pki.goog | 300 |
| time.ly | 0 issue sectigo.com | 300 |
| time.ly | 0 issue SomeCA.com | 300 |
| Host | Start of authority | TTL |
|---|---|---|
| time.ly | ns-261.awsdns-32.com awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 600 |
No reviews yet. Used time.ly? 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.
time.ly has no community safety rating yet. Its SSL certificate expired on 17 Oct 2024. See Security →
time.ly is registered through Libyan Spider Network (int). The public WHOIS record shows the registrant’s details. See WHOIS →
The registration expired on 1 Mar 2024. See Overview →
time.ly was registered on 1 Mar 2009, making it 17 years old. See Overview →
time.ly is served from 4 IP addresses, mainly on AS16509 Amazon.com Inc. in Germany. See Hosting →
Raw registry data for time.ly. May be redacted by privacy services.
Domain Name: time.ly Registry Domain ID: 33419-CoCCA Registry WHOIS Server: whois.nic.ly Updated Date: 2023-02-09T16:21:56.883Z Creation Date: 2009-03-01T22:00:00.0Z Registry Expiry Date: 2024-03-01T22:00:00.0Z Registrar Registration Expiration Date: 2024-03-01T22:00:00.0Z Registrar: Libyan Spider Network (int) Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.8448469791 Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: KtDtG-i6vcZ Registrant Name: Rik Logtenberg Registrant Organization: * Registrant Street: 6-2905 Lower Six Mile Road Registrant City: Nelson Registrant State/Province: British Columbia Registrant Postal Code: V1L 6L7 Registrant Country: CA Registrant Phone: +1.2508259499 Registrant Email: [email protected] Name Server: ns-1252.awsdns-28.org Name Server: ns-1820.awsdns-35.co.uk Name Server: ns-261.awsdns-32.com Name Server: ns-892.awsdns-47.net DNSSEC: unsigned >>> Last update of WHOIS database: 2023-11-08T07:07:11.516Z <<< For more information on Whois status codes, please visit https://icann.org/epp TERMS OF USE: You are not authorized to access or query our WHOIS database through the use of electronic processes that are high-volume and automated. This WHOIS database is provided by as a service to the internet community. The data is for information purposes only. We do not guarantee its accuracy. By submitting a WHOIS query, you agree to abide by the following terms of use: You agree that you may use this Data only for lawful purposes and that under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via e-mail, telephone, or facsimile; or (2) enable high volume, automated, electronic processes. The compilation, repackaging, dissemination or other use of this data is expressly prohibited.
The first response from http://www.time.ly, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with time.ly. 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.