crew.ly - dns.ninja
crew.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-13 13:00:13 | ||||||
| TXT | Generation Time: 1783947613 | ||||||
| SOA | dns.lttnet.netkhaleds@lttnet.net 2026-07-13 #13 | ||||||
Same first word
Similar names
DNS History
4 records (3 active, 1 former)
●NSa.dns.park.io2026-06-03 → 2026-07-13 · 2 obs
● 2026-07-13 14:50:08
●NSb.dns.park.io2026-06-03 → 2026-07-13 · 2 obs
● 2026-07-13 14:50:08
○A54.183.99.632015-12-23 → 2017-01-06 · 4 obs
● 2017-01-06 04:20:48
○ 2026-06-03 00:19:38
○ 2026-07-13 14:50:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ly | dns.lttnet.net, pch.ltt.ly, dns1.lttnet.net, ns-ly.afrinic.net... | 8 records |
| crew.ly | b.dns.park.io, a.dns.park.io | - |
✅ Authoritative Response
Server:23.23.95.213
NS records: b.dns.park.io, a.dns.park.io
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for crew.ly (unsigned zone)
⏱️ Timing
Total: 1253ms | 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 (dns.lttnet.net, dns1.lttnet.net, ns-ly.afrinic.net...)
Analysis
IP Addresses
crew.ly resolves to the IP addresses 34.200.211.86 and 54.147.18.156
Other host names — ec2-54-147-18-156.compute-1.amazonaws.com, ec2-34-200-211-86.compute-1.amazonaws.com, app.park.io and park.io — share IP numbers with crew.ly.
Name Servers
The NS records for crew.ly point to four name servers: ns-441.awsdns-55.com, ns-672.awsdns-20.net, ns-1348.awsdns-40.org and ns-1624.awsdns-11.co.uk.
crew.ly shares at least some of its name servers with other domains, including storageapplication.info, shogakukan-square.jp, zealy.io and two others.
The host names ns-441.awsdns-55.com, ns-672.awsdns-20.net, ns-1348.awsdns-40.org and ns-1624.awsdns-11.co.uk each resolve to two IP addresses: ns-441.awsdns-55.com resolves to 205.251.193.185 and 2600:9000:5301:b900::1; ns-672.awsdns-20.net resolves to 205.251.194.160 and 2600:9000:5302:a000::1; ns-1348.awsdns-40.org resolves to 205.251.197.68 and 2600:9000:5305:4400::1; ns-1624.awsdns-11.co.uk resolves to 205.251.198.88 and 2600:9000:5306:5800::1.
Mail Servers
crew.ly is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between crew.ly and other domains, including definedbio.com, visight.com, bcmanagement.us and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com points to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com points to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com points to 192.178.155.26 and 2607:f8b0:4004:c1b::1b.
alt1.aspmx.l.google.com points to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com points to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx2.googlemail.com and alt1.aspmx.l.google.com are host names that each point to 2800:3f0:4003:c0f::1b IP addresses.