lambda-code.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`lambda-code.com`

DNSSEC	⚠️ Not signed
NS	`ns-cloud-b1.googledomains.com` ⭐
		A	2001:4860:4802:32::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b1.googledomains.com`
		A	216.239.32.107^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-b1.googledomains.com`
NS	`ns-cloud-b2.googledomains.com`
		A	2001:4860:4802:34::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b2.googledomains.com`
		A	216.239.34.107^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-b2.googledomains.com`
NS	`ns-cloud-b3.googledomains.com`
		A	2001:4860:4802:36::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b3.googledomains.com`
		A	216.239.36.107^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-b3.googledomains.com`
NS	`ns-cloud-b4.googledomains.com`
		A	2001:4860:4802:38::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b4.googledomains.com`
		A	216.239.38.107^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-b4.googledomains.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c21::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pe-in-f26.1e100.net`
		A	192.178.155.27^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`hosting-site=sandbox-test-20250924`
TXT	`openai-domain-verification=dv-Z7Bh3ZQjbOj5FRoLGr9X5Ck0`
SOA	`ns-cloud-b1.googledomains.com`cloud-dns-hostmaster@google.com serial=5

`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=1790711189

Same first word

lambda-code.com

Previous names

Next names

DNS History

14 records (9 active, 5 former)

●NSns-cloud-b1.googledomains.com2026-09-10 → 2026-09-29 · 3 obs

○ 2017-06-28 10:21:04
● 2026-09-10 00:28:54
● 2026-09-29 20:12:20

●NSns-cloud-b2.googledomains.com2026-09-10 → 2026-09-29 · 3 obs

○ 2017-06-28 10:21:04
● 2026-09-10 00:28:54
● 2026-09-29 20:12:20

●NSns-cloud-b3.googledomains.com2026-09-10 → 2026-09-29 · 3 obs

○ 2017-06-28 10:21:04
● 2026-09-10 00:28:54
● 2026-09-29 20:12:20

●NSns-cloud-b4.googledomains.com2026-09-10 → 2026-09-29 · 3 obs

○ 2017-06-28 10:21:04
● 2026-09-10 00:28:54
● 2026-09-29 20:12:20

○NSns01.one.com2016-12-13 → 2017-06-28 · 4 obs

● 2016-12-13 17:30:08
● 2017-06-28 10:21:04
○ 2026-09-10 00:28:54
○ 2026-09-29 20:12:20

○NSns02.one.com2016-12-13 → 2017-06-28 · 4 obs

● 2016-12-13 17:30:08
● 2017-06-28 10:21:04
○ 2026-09-10 00:28:54
○ 2026-09-29 20:12:20

●MXalt1.aspmx.l.google.com2026-09-10 → 2026-09-29 · 3 obs

○ 2017-06-28 10:21:04
● 2026-09-10 00:28:54
● 2026-09-29 20:12:20

●MXalt2.aspmx.l.google.com2026-09-10 → 2026-09-29 · 3 obs

○ 2017-06-28 10:21:04
● 2026-09-10 00:28:54
● 2026-09-29 20:12:20

●MXalt3.aspmx.l.google.com2026-09-10 → 2026-09-29 · 3 obs

○ 2017-06-28 10:21:04
● 2026-09-10 00:28:54
● 2026-09-29 20:12:20

●MXalt4.aspmx.l.google.com2026-09-10 → 2026-09-29 · 3 obs

○ 2017-06-28 10:21:04
● 2026-09-10 00:28:54
● 2026-09-29 20:12:20

●MXaspmx.l.google.com2026-09-10 → 2026-09-29 · 3 obs

○ 2017-06-28 10:21:04
● 2026-09-10 00:28:54
● 2026-09-29 20:12:20

○MXmxcluster1.one.com2016-12-13 → 2017-06-28 · 4 obs

● 2016-12-13 17:30:08
● 2017-06-28 10:21:04
○ 2026-09-10 00:28:54
○ 2026-09-29 20:12:20

○MXmxcluster2.one.com2016-12-13 → 2017-06-28 · 4 obs

● 2016-12-13 17:30:08
● 2017-06-28 10:21:04
○ 2026-09-10 00:28:54
○ 2026-09-29 20:12:20

○A46.30.215.312016-12-13 → 2017-06-28 · 4 obs

● 2016-12-13 17:30:08
● 2017-06-28 10:21:04
○ 2026-09-10 00:28:54
○ 2026-09-29 20:12:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net, g.gtld-servers.net...	-
lambda-code.com	ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.32.107

NS records: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 669ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-cloud-b3.googledomains.com, ns-cloud-b1.googledomains.com...`
MX	5	`alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)...`
TXT	2	`hosting-site=sandbox-test-20250924, openai-domain-verification=dv-Z7Bh3ZQjbO`
SOA	1	`ns-cloud-b1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-b1.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com...)

Analysis

Name Servers

lambda-code.com has four authoritative name servers: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com.

lambda-code.com shares at least some of its name servers with other domains, including studiozega.com, lepleasuredome.com, photosfrommarss.com and two others.

The host names ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com each resolve to two IP addresses: ns-cloud-b1.googledomains.com resolves to 216.239.32.107 and 2001:4860:4802:32::6b; ns-cloud-b2.googledomains.com resolves to 216.239.34.107 and 2001:4860:4802:34::6b; ns-cloud-b3.googledomains.com resolves to 216.239.36.107 and 2001:4860:4802:36::6b; ns-cloud-b4.googledomains.com resolves to 216.239.38.107 and 2001:4860:4802:38::6b.

Mail Servers

lambda-code.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

lambda-code.com shares mail servers — at least in part — with other domains, including nemaa.org, mrowghani.com, kivinen.se and two others.

These mail servers are frequently paired with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.

Host names with two IP numbers:

aspmx.l.google.com resolves to 192.178.155.27 and 2607:f8b0:4004:c21::1a.

alt1.aspmx.l.google.com resolves to 192.178.234.26 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1b.