calendar.ly - robtex.com
calendar.ly
ly
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | dns1.lttnet.net ⭐ | ||||||
| NS | dns.lttnet.net | ||||||
| NS | ns-ly.afrinic.net | ||||||
| NS | pch.ltt.ly | ||||||
| NS | phloem.uoregon.edu | ||||||
| TXT | Generation Time ISO 8601: 2026-07-15 19:00:17 | ||||||
| TXT | Generation Time: 1784142017 | ||||||
| SOA | dns.lttnet.netkhaleds@lttnet.net 2026-07-15 #21 | ||||||
Same first word
Similar names
DNS History
7 records (3 active, 4 former)
●NSa.dns.park.io2026-06-08 → 2026-07-15 · 3 obs
● 2026-06-08 03:20:02
● 2026-07-15 20:33:30
●NSb.dns.park.io2026-06-08 → 2026-07-15 · 3 obs
● 2026-06-08 03:20:02
● 2026-07-15 20:33:30
○NSns1.digitalocean.com2018-07-18 → 2018-07-18 · 3 obs
○ 2026-06-08 03:20:02
○ 2026-07-15 20:33:30
○NSns2.digitalocean.com2018-07-18 → 2018-07-18 · 3 obs
○ 2026-06-08 03:20:02
○ 2026-07-15 20:33:30
○NSns3.digitalocean.com2018-07-18 → 2018-07-18 · 3 obs
○ 2026-06-08 03:20:02
○ 2026-07-15 20:33:30
○A188.226.217.2022018-07-18 → 2018-07-18 · 3 obs
○ 2026-06-08 03:20:02
○ 2026-07-15 20:33:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ly | pch.ltt.ly, ns-ly.afrinic.net, dns.lttnet.net, dns1.lttnet.net... | 8 records |
| calendar.ly | b.dns.park.io, a.dns.park.io | - |
✅ Authoritative Response
Server:54.225.121.213
NS records: b.dns.park.io, a.dns.park.io
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for calendar.ly (unsigned zone)
⏱️ Timing
Total: 988ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| CNAME | 1 | park.io |
| SOA | 1 | a.dns.park.io 2014070706 |
📌 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
calendar.ly points to the IP addresses 34.199.103.47 and 34.200.211.86
Among others, ec2-34-200-211-86.compute-1.amazonaws.com, app.park.io, ec2-34-199-103-47.compute-1.amazonaws.com and park.io resolve to the same IP numbers as calendar.ly.
Name Servers
The authoritative name servers for calendar.ly are ns-441.awsdns-55.com, ns-672.awsdns-20.net, ns-1348.awsdns-40.org and ns-1624.awsdns-11.co.uk.
There is at least partial name server overlap between calendar.ly and other domains — wareferees.org, nfe-cidades.com.br, verinthms.com and two more among them.
All four hostnames — ns-441.awsdns-55.com, ns-672.awsdns-20.net, ns-1348.awsdns-40.org and ns-1624.awsdns-11.co.uk — resolve to two IP numbers apiece: ns-441.awsdns-55.com to 205.251.193.185 and 2600:9000:5301:b900::1; ns-672.awsdns-20.net to 205.251.194.160 and 2600:9000:5302:a000::1; ns-1348.awsdns-40.org to 205.251.197.68 and 2600:9000:5305:4400::1; ns-1624.awsdns-11.co.uk to 205.251.198.88 and 2600:9000:5306:5800::1.
Mail Servers
calendar.ly has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
calendar.ly has at least partial mail server overlap with other domains such as matrixmkt.com.mx, raptorvault.com, roveelectric.com and two more.
These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt4.aspmx.l.google.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c23::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.