api.time.ly - dns.ninja

api.time.ly

DNSSEC⚠️ Not signed
A34.210.35.140πŸ‡ΊπŸ‡Έ Amazon34.208.0.0/12 EC2 PDX prefix
PTRec2-34-210-35-140.us-west-2.compute.amazonaws.com
A54.212.128.104πŸ‡ΊπŸ‡Έ Amazon54.212.0.0/16 EC2 PDX prefix

time.ly

DNSSEC⚠️ Not signed
A18.238.4.57πŸ‡ΊπŸ‡Έ Amazon18.238.4.0/22
A18.238.4.61πŸ‡ΊπŸ‡Έ Amazon18.238.4.0/22
A18.238.4.66πŸ‡ΊπŸ‡Έ Amazon18.238.4.0/22
A18.238.4.70πŸ‡ΊπŸ‡Έ Amazon18.238.4.0/22
NSns-261.awsdns-32.com ⭐
NSns-1252.awsdns-28.org
NSns-1820.awsdns-35.co.uk
NSns-892.awsdns-47.net
MXaspmx.l.google.com ⭐
MXalt1.aspmx.l.google.com(5)
MXalt2.aspmx.l.google.com(5)
MXalt3.aspmx.l.google.com(10)
MXalt4.aspmx.l.google.com(10)
TXTMS=5848C8DDFFAD40EA3EC503120CD30058B3A79497
TXTgoogle-site-verification=UM3BXAYEmhUSPYha4JzdTHeyqtuabh8pqlWULN216Vg
TXTgoogle-site-verification=V7GSXh3ETg2B11bXBaVddbB570ieYBCgLJmdZIdJ4kg
TXTv=spf1 include:amazonses.com include:_spf.google.com include:zcsend.net inclu...
SOAns-261.awsdns-32.comawsdns-hostmaster@amazon.com serial=1
rank #76711 globally
rank #37 in the tld

time.ly

Timely (time.ly) is a commercial event management and calendar software platform, used by organizations, universities, and communities to publish and manage event listings online. It is operated by a private software company under the.lyccTLD (Libya), chosen for the "time.ly" wordplay rather than any connection to Libya.

Key facts

  • Owner / operator: Timely (private software company)
  • TLD:.lyβ€” Libya (ccTLD, popularly used for domain hacks)
  • Primary purpose: event calendar / event management SaaS platform
  • Status: active

Related domains

  • Marketing and product pages may also reference alternate spellings such asgettimely.com, commonly used by companies with.lydomain hacks to provide a conventional gTLD alternative.
πŸ”’ HSTS Preload (+subdomains)
πŸ“ˆ Tranco rank: #122,868

Same first word

Similar names

DNS History

13 records (2 active, 11 former)

2017201820192020202120222023202420252026A34.210.35.14054.212.128.104100.22.29.228100.23.2.177184.32.219.18634.209.74.19135.86.29.8744.224.220.7152.11.67.10952.34.7.3452.41.84.16752.42.160.81CNAMEapi-lb-1264418590.us-west-2.elb.amazonaws.com
β—‹A100.22.29.2282026-04-11 β†’ 2026-04-11 Β· 4 obs
β—‹ 2016-12-28 20:39:30
● 2026-04-11 04:04:06
β—‹ 2026-05-27 03:58:18
β—‹ 2026-07-25 15:24:18
β—‹A100.23.2.1772026-05-27 β†’ 2026-05-27 Β· 4 obs
β—‹ 2026-04-11 04:04:06
● 2026-05-27 03:58:18
β—‹ 2026-06-01 07:46:02
β—‹ 2026-07-25 15:24:18
β—‹A184.32.219.1862026-06-01 β†’ 2026-06-01 Β· 3 obs
β—‹ 2026-05-27 03:58:18
● 2026-06-01 07:46:02
β—‹ 2026-07-25 15:24:18
β—‹A34.209.74.1912026-04-11 β†’ 2026-04-11 Β· 4 obs
β—‹ 2016-12-28 20:39:30
● 2026-04-11 04:04:06
β—‹ 2026-05-27 03:58:18
β—‹ 2026-07-25 15:24:18
●A34.210.35.1402026-07-25 β†’ 2026-07-25 Β· 2 obs
β—‹ 2026-06-01 07:46:02
● 2026-07-25 15:24:18
β—‹A35.86.29.872026-04-11 β†’ 2026-07-25 Β· 2 obs
β—‹ 2026-04-11 04:04:06
β—‹ 2026-07-25 15:24:18
β—‹A44.224.220.712026-05-27 β†’ 2026-05-27 Β· 4 obs
β—‹ 2026-04-11 04:04:06
● 2026-05-27 03:58:18
β—‹ 2026-06-01 07:46:02
β—‹ 2026-07-25 15:24:18
β—‹A52.11.67.1092016-12-28 β†’ 2016-12-28 Β· 3 obs
● 2016-12-28 20:39:30
β—‹ 2026-04-11 04:04:06
β—‹ 2026-07-25 15:24:18
β—‹A52.34.7.342016-12-28 β†’ 2016-12-28 Β· 3 obs
● 2016-12-28 20:39:30
β—‹ 2026-04-11 04:04:06
β—‹ 2026-07-25 15:24:18
β—‹A52.41.84.1672026-04-11 β†’ 2026-07-25 Β· 2 obs
β—‹ 2026-04-11 04:04:06
β—‹ 2026-07-25 15:24:18
β—‹A52.42.160.812026-06-01 β†’ 2026-06-01 Β· 3 obs
β—‹ 2026-05-27 03:58:18
● 2026-06-01 07:46:02
β—‹ 2026-07-25 15:24:18
●A54.212.128.1042026-07-25 β†’ 2026-07-25 Β· 2 obs
β—‹ 2026-06-01 07:46:02
● 2026-07-25 15:24:18
β—‹CNAMEapi-lb-1264418590.us-west-2.elb.amazonaws.com2016-12-28 β†’ 2016-12-28 Β· 3 obs
● 2016-12-28 20:39:30
β—‹ 2026-04-11 04:04:06
β—‹ 2026-07-25 15:24:18

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
lypch.ltt.ly, dns.lttnet.net, dns1.lttnet.net, ns-ly.afrinic.net...8 records
time.lyns-1252.awsdns-28.org, ns-892.awsdns-47.net, ns-261.awsdns-32.com, ns-1820.awsdns-35.co.uk-

βœ… Authoritative Response

Server:205.251.199.28

NS records: ns-1252.awsdns-28.org, ns-892.awsdns-47.net, ns-261.awsdns-32.com, ns-1820.awsdns-35.co.uk

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for time.ly (unsigned zone)

⏱️ Timing

Total: 910ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A234.210.35.140, 54.212.128.104

πŸ“Œ Glue Records Collected

Total: 8

In-bailiwick: 2 (pch.ltt.ly, pch.ltt.ly)

Out-of-bailiwick: 6 (phloem.uoregon.edu, ns-ly.afrinic.net, dns1.lttnet.net...)

Analysis

IP Addresses

api.time.ly directs to two IP numbers, 34.210.35.140 and 54.212.128.104

Host names like ec2-34-210-35-140.us-west-2.compute.amazonaws.com are further examples that share IP numbers with api.time.ly.