lenry.com - dns.ninja
lenry.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 86.105.245.69🇳🇱 TRANSIP-AS86.105.244.0/22 TransIP BV Amsterdam, The Netherlands | ||||||
| PTR | 86-105-245-69.haip.transip.net | ||||||
| NS | ns1.eftydns.com ⭐ | ||||||
| A | 87.253.137.197🇳🇱 TRANSIP-AS87.253.128.0/19 TransIP BV Amsterdam, The Netherlands | ||||||
| PTR | 87-253-137-197.colo.transip.net | ||||||
| NS | ns2.eftydns.com | ||||||
| A | 136.144.254.183🇳🇱 TRANSIP-AS136.144.128.0/17 TransIP BV Amsterdam, The Netherlands | ||||||
| PTR | 136-144-254-183.colo.transip.net | ||||||
| SOA | ns1.eftydns.comhostmaster@lenry.com 2026-06-11 #1 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1781384488 | ||||||
Same first word
Similar names
DNS History
13 records (3 active, 10 former)
○NSbuy.internettraffic.com2015-11-27 → 2016-05-03 · 6 obs
● 2015-11-27 06:10:02
○ 2016-02-24 04:00:04
● 2016-05-03 17:10:52
○ 2017-01-24 16:51:48
○ 2026-06-13 21:19:04
●NSns1.eftydns.com2026-06-13 → 2026-06-13 · 2 obs
● 2026-06-13 21:19:04
○NSns1.sedoparking.com2015-08-12 → 2015-08-12 · 3 obs
○ 2015-11-27 06:10:02
○ 2026-06-13 21:19:04
○NSns1.uniregistrymarket.link2017-01-24 → 2019-12-25 · 4 obs
● 2017-01-24 16:51:48
● 2019-12-25 02:01:16
○ 2026-06-13 21:19:04
●NSns2.eftydns.com2026-06-13 → 2026-06-13 · 2 obs
● 2026-06-13 21:19:04
○NSns2.sedoparking.com2015-08-12 → 2015-08-12 · 3 obs
○ 2015-11-27 06:10:02
○ 2026-06-13 21:19:04
○NSns2.uniregistrymarket.link2017-01-24 → 2019-12-25 · 4 obs
● 2017-01-24 16:51:48
● 2019-12-25 02:01:16
○ 2026-06-13 21:19:04
○NSsell.internettraffic.com2015-11-27 → 2016-05-03 · 6 obs
● 2015-11-27 06:10:02
○ 2016-02-24 04:00:04
● 2016-05-03 17:10:52
○ 2017-01-24 16:51:48
○ 2026-06-13 21:19:04
○MXmail.nickstel.com2015-08-12 → 2015-08-12 · 3 obs
○ 2015-11-27 06:10:02
○ 2026-06-13 21:19:04
○A69.172.201.1532016-05-03 → 2019-12-25 · 4 obs
● 2016-05-03 17:10:52
● 2019-12-25 02:01:16
○ 2026-06-13 21:19:04
○A69.172.201.2082015-11-27 → 2015-11-27 · 4 obs
● 2015-11-27 06:10:02
○ 2016-02-24 04:00:04
○ 2026-06-13 21:19:04
○A72.52.4.912015-08-12 → 2015-08-12 · 3 obs
○ 2015-11-27 06:10:02
○ 2026-06-13 21:19:04
●A86.105.245.692026-06-13 → 2026-06-13 · 2 obs
● 2026-06-13 21:19:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| lenry.com | ns1.eftydns.com, ns2.eftydns.com | 2 records |
✅ Authoritative Response
Server:87.253.137.197
NS records: ns1.eftydns.com, ns2.eftydns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for lenry.com (unsigned zone)
⏱️ Timing
Total: 341ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 86.105.245.69 |
| NS | 2 | ns1.eftydns.com, ns2.eftydns.com |
| SOA | 1 | ns1.eftydns.com hostmaster.lenry.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.eftydns.com, ns2.eftydns.com)
Analysis
IP Addresses
lenry.com resolves to one IP address: 86.105.245.69.
cabinlove.com, onlinestoragecalculator.com, djmak.com and two other host names share IP numbers with lenry.com.
Name Servers
The NS records for lenry.com delegate to ns1.eftydns.com and ns2.eftydns.com.
lenry.com uses the same name servers as several other domains — among them kyftz.com, zbabet.com, botxr.com and two more.
lenry.com has a partial name server overlap with other domains — among them anky.xyz and rfua.com.
It is common to see these name servers used together with name servers dns1.a.io and dns2.a.io.
ns1.eftydns.com directs to 87.253.137.197 and ns2.eftydns.com directs to 136.144.254.183; each host name points to exactly one IP number.