lambda.in - dns.ninja

lambda.in

DNSSEC⚠️ Not signed
NSns1.atom.com ⚠️ Not in zone NS records
A44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix
PTRec2-44-219-81-145.compute-1.amazonaws.com
NSns2.atom.com ⚠️ Not in zone NS records
A50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix
PTRec2-50-19-240-86.compute-1.amazonaws.com

in

DNSSEC🔒 Signed (DS record present)
NSns01.trs-dns.com
NSns.trs-dns.com
NSns01.trs-dns.net
NSns1.registry.in ⚠️ Not in parent delegation
NSns10.trs-dns.info
NSns10.trs-dns.org
NSns2.registry.in ⚠️ Not in parent delegation
NSns3.registry.in ⚠️ Not in parent delegation
NSns4.registry.in ⚠️ Not in parent delegation
SOAns.trs-dns.comtrs-ops@tucows.com serial=1780688159

Same first word

Similar names

DNS History

14 records (2 active, 12 former)

20162017201820192020202120222023202420252026NSns1.atom.comns2.atom.coma.dns.gandi.netb.dns.gandi.netc.dns.gandi.netns1.bodis.comns2.bodis.comMXfb.mail.gandi.netmx76.m2bp.commx76.mb1p.comspool.mail.gandi.netA199.59.242.150199.59.243.120217.70.184.38
NSa.dns.gandi.net2015-06-11 → 2015-06-11 · 3 obs
● 2015-06-11 06:26:28
○ 2015-10-23 16:08:20
○ 2026-06-05 19:40:58
NSb.dns.gandi.net2015-06-11 → 2015-06-11 · 3 obs
● 2015-06-11 06:26:28
○ 2015-10-23 16:08:20
○ 2026-06-05 19:40:58
NSc.dns.gandi.net2015-06-11 → 2015-06-11 · 3 obs
● 2015-06-11 06:26:28
○ 2015-10-23 16:08:20
○ 2026-06-05 19:40:58
NSns1.atom.com2026-04-03 → 2026-06-05 · 3 obs
○ 2017-03-17 11:56:02
● 2026-04-03 06:49:02
● 2026-06-05 19:40:58
NSns1.bodis.com2015-12-09 → 2017-03-17 · 5 obs
○ 2015-10-23 16:08:20
● 2015-12-09 12:16:42
● 2017-03-17 11:56:02
○ 2026-04-03 06:49:02
○ 2026-06-05 19:40:58
NSns2.atom.com2026-04-03 → 2026-06-05 · 3 obs
○ 2017-03-17 11:56:02
● 2026-04-03 06:49:02
● 2026-06-05 19:40:58
NSns2.bodis.com2015-12-09 → 2017-03-17 · 5 obs
○ 2015-10-23 16:08:20
● 2015-12-09 12:16:42
● 2017-03-17 11:56:02
○ 2026-04-03 06:49:02
○ 2026-06-05 19:40:58
MXfb.mail.gandi.net2015-06-11 → 2015-06-11 · 3 obs
● 2015-06-11 06:26:28
○ 2015-10-23 16:08:20
○ 2026-06-05 19:40:58
MXmx76.m2bp.com2017-03-17 → 2017-03-17 · 4 obs
○ 2015-10-23 16:08:20
● 2017-03-17 11:56:02
○ 2026-04-03 06:49:02
○ 2026-06-05 19:40:58
MXmx76.mb1p.com2017-03-17 → 2017-03-17 · 4 obs
○ 2015-10-23 16:08:20
● 2017-03-17 11:56:02
○ 2026-04-03 06:49:02
○ 2026-06-05 19:40:58
MXspool.mail.gandi.net2015-06-11 → 2015-06-11 · 3 obs
● 2015-06-11 06:26:28
○ 2015-10-23 16:08:20
○ 2026-06-05 19:40:58
A199.59.242.1502017-03-17 → 2017-03-17 · 4 obs
○ 2016-07-10 20:59:30
● 2017-03-17 11:56:02
○ 2026-04-03 06:49:02
○ 2026-06-05 19:40:58
A199.59.243.1202015-12-09 → 2016-07-10 · 5 obs
○ 2015-10-23 16:08:20
● 2015-12-09 12:16:42
● 2016-07-10 20:59:30
○ 2017-03-17 11:56:02
○ 2026-06-05 19:40:58
A217.70.184.382015-06-11 → 2015-06-11 · 3 obs
● 2015-06-11 06:26:28
○ 2015-10-23 16:08:20
○ 2026-06-05 19:40:58

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
inns01.trs-dns.com, ns10.trs-dns.info, ns10.trs-dns.org, ns01.trs-dns.net-
lambda.inns1.atom.com, ns2.atom.com-

✅ Authoritative Response

Server:44.219.81.145

NS records: ns1.atom.com, ns2.atom.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for lambda.in (unsigned zone)

⏱️ Timing

Total: 387ms | Queries: -

📄 Records

TypeCountSample Data

Analysis

Name Servers

lambda.in is served by two delegated name servers, ns1.atom.com and ns2.atom.com.

lambda.in uses the same name servers as several other domains — among them ripples.me, guffu.com, wfmanager.com and two more.

lambda.in has at least partial name server overlap with other domains, such as bsaten.com, askuf.com, citrusi.com and two others.

It is common to see these name servers used together with name servers ns1.afternic.com and ns2.afternic.com.

ns1.atom.com directs to 44.219.81.145 and ns2.atom.com directs to 50.19.240.86; each host name points to exactly one IP number.