lambda-bio.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`lambda-bio.com`

DNSSEC	⚠️ Not signed
A	18.197.187.210^{🇩🇪 Amazon18.196.0.0/15 EC2 FRA prefix}
		PTR	`ec2-18-197-187-210.eu-central-1.compute.amazonaws.com`
NS	`ns-1363.awsdns-42.org` ⭐
		A	2600:9000:5305:5300::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1363.awsdns-42.org`
		A	205.251.197.83^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1363.awsdns-42.org`
NS	`ns-1800.awsdns-33.co.uk`
		A	2600:9000:5307:800::1^{🇺🇸 Amazon2600:9000:5307::/48 - CloudFront}
			PTR	`ns-1800.awsdns-33.co.uk`
		A	205.251.199.8^{🇺🇸 Amazon205.251.199.0/24 prefix}
			PTR	`ns-1800.awsdns-33.co.uk`
NS	`ns-226.awsdns-28.com`
		A	2600:9000:5300:e200::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-226.awsdns-28.com`
		A	205.251.192.226^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-226.awsdns-28.com`
NS	`ns-764.awsdns-31.net`
		A	2600:9000:5302:fc00::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-764.awsdns-31.net`
		A	205.251.194.252^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-764.awsdns-31.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c27::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadsk-in-f26.1e100.net`
		A	142.251.163.26^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.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.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`brevo-code:ba69983c06cfc90be0c5789bd9e85e3d`
TXT	`google-site-verification=KXkjGqMJ9c36Ev5sZe1zRlGIRWiSXjEoXfwk79XkG40`
TXT	`v=spf1 include:246836062.spf05.hubspotemail.net -all`
SOA	`ns-1363.awsdns-42.org`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=1788043235

Same first word

lambda-bio.com

Previous names

Next names

DNS History

15 records (10 active, 5 former)

●NSns-1363.awsdns-42.org2026-08-26 → 2026-08-29 · 3 obs

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-08-29 22:47:50

●NSns-1800.awsdns-33.co.uk2026-08-26 → 2026-08-29 · 3 obs

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-08-29 22:47:50

●NSns-226.awsdns-28.com2026-08-26 → 2026-08-29 · 3 obs

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-08-29 22:47:50

●NSns-764.awsdns-31.net2026-08-26 → 2026-08-29 · 3 obs

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-08-29 22:47:50

○NSns1.mdnsservice.com2015-06-06 → 2017-06-26 · 4 obs

● 2015-06-06 17:50:06
● 2017-06-26 17:32:16
○ 2026-08-26 20:42:54
○ 2026-08-29 22:47:50

○NSns2.mdnsservice.com2015-06-06 → 2017-06-26 · 4 obs

● 2015-06-06 17:50:06
● 2017-06-26 17:32:16
○ 2026-08-26 20:42:54
○ 2026-08-29 22:47:50

○NSns3.mdnsservice.com2015-06-06 → 2017-06-26 · 4 obs

● 2015-06-06 17:50:06
● 2017-06-26 17:32:16
○ 2026-08-26 20:42:54
○ 2026-08-29 22:47:50

●MXalt1.aspmx.l.google.com2026-08-26 → 2026-08-29 · 3 obs

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-08-29 22:47:50

●MXalt2.aspmx.l.google.com2026-08-26 → 2026-08-29 · 3 obs

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-08-29 22:47:50

●MXalt3.aspmx.l.google.com2026-08-26 → 2026-08-29 · 3 obs

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-08-29 22:47:50

●MXalt4.aspmx.l.google.com2026-08-26 → 2026-08-29 · 3 obs

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-08-29 22:47:50

●MXaspmx.l.google.com2026-08-26 → 2026-08-29 · 3 obs

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-08-29 22:47:50

○MXmx.lambda-bio.com2015-06-06 → 2017-06-26 · 4 obs

● 2015-06-06 17:50:06
● 2017-06-26 17:32:16
○ 2026-08-26 20:42:54
○ 2026-08-29 22:47:50

●A18.197.187.2102026-08-26 → 2026-08-29 · 3 obs

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-08-29 22:47:50

○A216.40.47.172015-06-06 → 2017-06-26 · 4 obs

● 2015-06-06 17:50:06
● 2017-06-26 17:32:16
○ 2026-08-26 20:42:54
○ 2026-08-29 22:47:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
lambda-bio.com	ns-226.awsdns-28.com, ns-764.awsdns-31.net, ns-1800.awsdns-33.co.uk, ns-1363.awsdns-42.org	2 records

✅ Authoritative Response

Server:205.251.197.83

NS records: ns-226.awsdns-28.com, ns-764.awsdns-31.net, ns-1800.awsdns-33.co.uk, ns-1363.awsdns-42.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for lambda-bio.com (unsigned zone)

⏱️ Timing

Total: 491ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`18.197.187.210`
NS	4	`ns-1363.awsdns-42.org, ns-1800.awsdns-33.co.uk...`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	3	`brevo-code:ba69983c06cfc90be0c5789bd9e85, google-site-verification=KXkjGqMJ9c36Ev5...`
SOA	1	`ns-1363.awsdns-42.org awsdns-hostmaster.`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-226.awsdns-28.com, ns-226.awsdns-28.com)

Analysis

IP Addresses

lambda-bio.com resolves to one IP address: 18.197.187.210.

Name Servers

The authoritative name servers for lambda-bio.com are ns-226.awsdns-28.com, ns-764.awsdns-31.net, ns-1363.awsdns-42.org and ns-1800.awsdns-33.co.uk.

lambda-bio.com shares at least some of its name servers with other domains, including zeristor.net, (0x636f636b)ram.us, setatime.co and two others.

The host names ns-226.awsdns-28.com, ns-764.awsdns-31.net, ns-1363.awsdns-42.org and ns-1800.awsdns-33.co.uk each resolve to two IP addresses: ns-226.awsdns-28.com resolves to 205.251.192.226 and 2600:9000:5300:e200::1; ns-764.awsdns-31.net resolves to 205.251.194.252 and 2600:9000:5302:fc00::1; ns-1363.awsdns-42.org resolves to 205.251.197.83 and 2600:9000:5305:5300::1; ns-1800.awsdns-33.co.uk resolves to 205.251.199.8 and 2600:9000:5307:800::1.

Mail Servers

lambda-bio.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-bio.com has at least partial mail server overlap with other domains such as coffeeconex.com, retribal.com, growimpacts.com and two more.

These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 4 others.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com has two IP addresses: 142.251.163.26 and 2607:f8b0:4004:c27::1a.

alt1.aspmx.l.google.com has two IP addresses: 192.178.234.27 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com has two IP addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com has two IP addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com has two IP addresses: 172.253.157.27 and 2a00:1450:400c:c23::1b.