lambda.in - dns.ninja
lambda.in
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.atom.com ⚠️ Not in zone NS records | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com ⚠️ Not in zone NS records | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns.trs-dns.com ⭐ | ||||||
| NS | ns1.registry.in | ||||||
| NS | ns2.registry.in | ||||||
| NS | ns3.registry.in | ||||||
| NS | ns4.registry.in | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1784837452 | ||||||
Same first word
Similar names
DNS History
14 records (2 active, 12 former)
○NSa.dns.gandi.net2015-06-11 → 2015-06-11 · 3 obs
○ 2015-10-23 16:08:20
○ 2026-07-23 20:37:40
○NSb.dns.gandi.net2015-06-11 → 2015-06-11 · 3 obs
○ 2015-10-23 16:08:20
○ 2026-07-23 20:37:40
○NSc.dns.gandi.net2015-06-11 → 2015-06-11 · 3 obs
○ 2015-10-23 16:08:20
○ 2026-07-23 20:37:40
●NSns1.atom.com2026-04-03 → 2026-07-23 · 3 obs
● 2026-04-03 06:49:02
● 2026-07-23 20:37:40
○NSns1.bodis.com2015-12-09 → 2017-03-17 · 5 obs
● 2015-12-09 12:16:42
● 2017-03-17 11:56:02
○ 2026-04-03 06:49:02
○ 2026-07-23 20:37:40
●NSns2.atom.com2026-04-03 → 2026-07-23 · 3 obs
● 2026-04-03 06:49:02
● 2026-07-23 20:37:40
○NSns2.bodis.com2015-12-09 → 2017-03-17 · 5 obs
● 2015-12-09 12:16:42
● 2017-03-17 11:56:02
○ 2026-04-03 06:49:02
○ 2026-07-23 20:37:40
○MXfb.mail.gandi.net2015-06-11 → 2015-06-11 · 3 obs
○ 2015-10-23 16:08:20
○ 2026-07-23 20:37:40
○MXmx76.m2bp.com2017-03-17 → 2017-03-17 · 4 obs
● 2017-03-17 11:56:02
○ 2026-04-03 06:49:02
○ 2026-07-23 20:37:40
○MXmx76.mb1p.com2017-03-17 → 2017-03-17 · 4 obs
● 2017-03-17 11:56:02
○ 2026-04-03 06:49:02
○ 2026-07-23 20:37:40
○MXspool.mail.gandi.net2015-06-11 → 2015-06-11 · 3 obs
○ 2015-10-23 16:08:20
○ 2026-07-23 20:37:40
○A199.59.242.1502017-03-17 → 2017-03-17 · 4 obs
● 2017-03-17 11:56:02
○ 2026-04-03 06:49:02
○ 2026-07-23 20:37:40
○A199.59.243.1202015-12-09 → 2016-07-10 · 5 obs
● 2015-12-09 12:16:42
● 2016-07-10 20:59:30
○ 2017-03-17 11:56:02
○ 2026-07-23 20:37:40
○A217.70.184.382015-06-11 → 2015-06-11 · 3 obs
○ 2015-10-23 16:08:20
○ 2026-07-23 20:37:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns2.registry.in, ns3.registry.in, ns4.registry.in, ns1.registry.in | - |
| lambda.in | ns1.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: 397ms | Queries: -
📄 Records
| Type | Count | Sample 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 discountcar.co, ripples.me, nfugroup.com and two more.
lambda.in has at least partial name server overlap with other domains, such as bsaten.com, askuf.com, energyredo.com and two others.
It is common to find these name servers paired with the name servers verification-refeskkalf4qgvebx3uk7a.ns101.verify.hn.
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.