answer.ly - dns.ninja

answer.ly

DNSSEC⚠️ Not signed
NSa.dns.park.io ⚠️ Not in zone NS records
A23.23.95.213πŸ‡ΊπŸ‡Έ Amazon23.22.0.0/15 EC2 IAD prefix
PTRa.dns.park.io
NSb.dns.park.io ⚠️ Not in zone NS records
A54.225.121.213πŸ‡ΊπŸ‡Έ Amazon54.224.0.0/15 EC2 IAD prefix
PTRb.dns.park.io

ly

DNSSECπŸ”’ Signed (DS record present)
NSdns1.lttnet.net ⭐
NSdns.lttnet.net
NSns-ly.afrinic.net
NSpch.ltt.ly
NSphloem.uoregon.edu
TXTGeneration Time: 1781446004
TXTGeneration Time ISO 8601: 2026-06-14 14:06:44
SOAdns.lttnet.netkhaleds@lttnet.net 2026-06-14 #12

Previously MX for

Same first word

Similar names

DNS History

10 records (2 active, 8 former)

20162017201820192020202120222023202420252026NSa.dns.park.iob.dns.park.ions1.brandbucket.comns1.project.lyns2.brandbucket.comns2.project.lyMXanswer.lyA41.208.68.11454.183.99.63CNAMEpark.io
●NSa.dns.park.io2026-03-31 β†’ 2026-06-14 Β· 3 obs
β—‹ 2018-09-11 10:59:10
● 2026-03-31 01:29:20
● 2026-06-14 15:04:08
●NSb.dns.park.io2026-03-31 β†’ 2026-06-14 Β· 3 obs
β—‹ 2018-09-11 10:59:10
● 2026-03-31 01:29:20
● 2026-06-14 15:04:08
β—‹NSns1.brandbucket.com2018-09-11 β†’ 2018-09-11 Β· 4 obs
β—‹ 2017-02-09 02:52:40
● 2018-09-11 10:59:10
β—‹ 2026-03-31 01:29:20
β—‹ 2026-06-14 15:04:08
β—‹NSns1.project.ly2016-01-29 β†’ 2017-02-09 Β· 4 obs
● 2016-01-29 02:20:16
● 2017-02-09 02:52:40
β—‹ 2018-09-11 10:59:10
β—‹ 2026-06-14 15:04:08
β—‹NSns2.brandbucket.com2018-09-11 β†’ 2018-09-11 Β· 4 obs
β—‹ 2017-02-09 02:52:40
● 2018-09-11 10:59:10
β—‹ 2026-03-31 01:29:20
β—‹ 2026-06-14 15:04:08
β—‹NSns2.project.ly2016-01-29 β†’ 2017-02-09 Β· 4 obs
● 2016-01-29 02:20:16
● 2017-02-09 02:52:40
β—‹ 2018-09-11 10:59:10
β—‹ 2026-06-14 15:04:08
β—‹MXanswer.ly2016-01-29 β†’ 2017-02-09 Β· 4 obs
● 2016-01-29 02:20:16
● 2017-02-09 02:52:40
β—‹ 2018-09-11 10:59:10
β—‹ 2026-06-14 15:04:08
β—‹A41.208.68.1142016-01-29 β†’ 2017-02-09 Β· 5 obs
β—‹ 2015-08-20 08:38:18
● 2016-01-29 02:20:16
● 2017-02-09 02:52:40
β—‹ 2018-09-11 10:59:10
β—‹ 2026-06-14 15:04:08
β—‹A54.183.99.632015-08-20 β†’ 2018-09-11 Β· 6 obs
● 2015-08-20 08:38:18
β—‹ 2016-01-29 02:20:16
β—‹ 2017-02-09 02:52:40
● 2018-09-11 10:59:10
β—‹ 2026-03-31 01:29:20
β—‹ 2026-06-14 15:04:08
β—‹CNAMEpark.io2026-03-31 β†’ 2026-06-14 Β· 2 obs
β—‹ 2026-03-31 01:29:20
β—‹ 2026-06-14 15:04:08

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
lydns.lttnet.net, pch.ltt.ly, dns1.lttnet.net, ns-ly.afrinic.net...8 records
answer.lya.dns.park.io, b.dns.park.io-

βœ… Authoritative Response

Server:23.23.95.213

NS records: a.dns.park.io, b.dns.park.io

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for answer.ly (unsigned zone)

⏱️ Timing

Total: 523ms | Queries: -

πŸ“„ Records

TypeCountSample Data

πŸ“Œ 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

Name Servers

answer.ly uses two name servers for its delegation: a.dns.park.io and b.dns.park.io.

The name server configuration of answer.ly is shared with other domains, for instance filmai.to, qa.vc, alerts.io and two others.

The name servers for answer.ly overlap at least in part with those of other domains, including holidaycheck.co and 100.ag.

These name servers commonly appear alongside the name servers ns1.parkco1.neustar.biz and ns2.parkco1.neustar.biz.

Both a.dns.park.io and b.dns.park.io have a single IP address each β€” a.dns.park.io resolves to 23.23.95.213 while b.dns.park.io resolves to 54.225.121.213.