🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`lambdaencoding.com`

DNSSEC	⚠️ Not signed
NS	`ns-727.awsdns-26.net` ⭐
		A	2600:9000:5302:d700::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-727.awsdns-26.net`
		A	205.251.194.215^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-727.awsdns-26.net`
NS	`ns-1172.awsdns-18.org`
		A	2600:9000:5304:9400::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1172.awsdns-18.org`
		A	205.251.196.148^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1172.awsdns-18.org`
NS	`ns-1653.awsdns-14.co.uk`
		A	2600:9000:5306:7500::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1653.awsdns-14.co.uk`
		A	205.251.198.117^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1653.awsdns-14.co.uk`
NS	`ns-309.awsdns-38.com`
		A	2600:9000:5301:3500::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-309.awsdns-38.com`
		A	205.251.193.53^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-309.awsdns-38.com`
SOA	`ns-727.awsdns-26.net`awsdns-hostmaster@amazon.com serial=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.net`nstld@verisign-grs.com serial=1788623188

Same first word

lambdaencoding.com

Previous names

Next names

DNS History

4 records (4 active, 0 former)

●NSns-1172.awsdns-18.org2026-09-02 → 2026-09-05 · 2 obs

● 2026-09-02 11:14:22
● 2026-09-05 16:09:58

●NSns-1653.awsdns-14.co.uk2026-09-02 → 2026-09-05 · 2 obs

● 2026-09-02 11:14:22
● 2026-09-05 16:09:58

●NSns-309.awsdns-38.com2026-09-02 → 2026-09-05 · 2 obs

● 2026-09-02 11:14:22
● 2026-09-05 16:09:58

●NSns-727.awsdns-26.net2026-09-02 → 2026-09-05 · 2 obs

● 2026-09-02 11:14:22
● 2026-09-05 16:09:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
lambdaencoding.com	ns-727.awsdns-26.net, ns-309.awsdns-38.com, ns-1653.awsdns-14.co.uk, ns-1172.awsdns-18.org	2 records

✅ Authoritative Response

Server:205.251.194.215

NS records: ns-727.awsdns-26.net, ns-309.awsdns-38.com, ns-1653.awsdns-14.co.uk, ns-1172.awsdns-18.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for lambdaencoding.com (unsigned zone)

⏱️ Timing

Total: 659ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-1172.awsdns-18.org, ns-1653.awsdns-14.co.uk...`
SOA	1	`ns-727.awsdns-26.net awsdns-hostmaster.a`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-309.awsdns-38.com, ns-309.awsdns-38.com)

Analysis

Name Servers

The NS records for lambdaencoding.com point to four name servers: ns-309.awsdns-38.com, ns-727.awsdns-26.net, ns-1172.awsdns-18.org and ns-1653.awsdns-14.co.uk.

lambdaencoding.com has at least partial name server overlap with other domains, such as e8j4dr9u89.com, findus.fr, digiacre.com and two others.

ns-309.awsdns-38.com, ns-727.awsdns-26.net, ns-1172.awsdns-18.org and ns-1653.awsdns-14.co.uk all point to exactly two IP numbers each: ns-309.awsdns-38.com → 205.251.193.53 and 2600:9000:5301:3500::1; ns-727.awsdns-26.net → 205.251.194.215 and 2600:9000:5302:d700::1; ns-1172.awsdns-18.org → 205.251.196.148 and 2600:9000:5304:9400::1; ns-1653.awsdns-14.co.uk → 205.251.198.117 and 2600:9000:5306:7500::1.

lambdaencoding.com - dns.ninja