🛡️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	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	172.217.76.27^{🇺🇸 Google172.217.76.0/24}
			PTR	`yulhrp-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4025:402::1b^{🇳🇱 Google2a00:1450:4025::/48}
			PTR	`rb-in-f27.1e100.net`
		A	142.250.102.27^{🇺🇸 Google142.250.102.0/24}
			PTR	`rb-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4013:c1e::1b^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`yugrqzs-in-f27.1e100.net`
		A	192.178.213.26^{🇺🇸 Google192.178.213.0/24}
			PTR	`yugrqzs-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4001:c21::1b^{🇩🇪 Google2a00:1450:4001::/48}
			PTR	`lcfrai-in-f27.1e100.net`
		A	142.251.127.27^{🇺🇸 Google142.251.127.0/24}
			PTR	`lcfrai-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4025:4401::1b^{🇮🇪 Google2a00:1450:4025::/48}
			PTR	`yuskedq-in-f27.1e100.net`
		A	172.253.148.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yuskedq-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=1788265040

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-09-01 · 3 obs

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-09-01 12:21:26

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

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-09-01 12:21:26

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

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-09-01 12:21:26

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

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-09-01 12:21:26

○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-09-01 12:21:26

○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-09-01 12:21:26

○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-09-01 12:21:26

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

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-09-01 12:21:26

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

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-09-01 12:21:26

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

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-09-01 12:21:26

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

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-09-01 12:21:26

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

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-09-01 12:21:26

○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-09-01 12:21:26

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

○ 2017-06-26 17:32:16
● 2026-08-26 20:42:54
● 2026-09-01 12:21:26

○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-09-01 12:21:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.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: 549ms | 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 directs to one IP number, which is 18.197.187.210.

Name Servers

The domain lambda-bio.com is delegated to these four name servers: ns-226.awsdns-28.com, ns-764.awsdns-31.net, ns-1363.awsdns-42.org and ns-1800.awsdns-33.co.uk.

At least some of lambda-bio.com's name servers are shared with other domains, for example zeristor.net, (0x636f636b)ram.us, setatime.co and two more.

It is common for these name servers to be used in conjunction with the name servers ns-1926.awsdns-48.co.uk, ns-643.awsdns-16.net and ns-1102.awsdns-09.org.

Four hostnames, each resolving to a pair of IP addresses: ns-226.awsdns-28.com directs to 205.251.192.226 and 2600:9000:5300:e200::1; ns-764.awsdns-31.net directs to 205.251.194.252 and 2600:9000:5302:fc00::1; ns-1363.awsdns-42.org directs to 205.251.197.83 and 2600:9000:5305:5300::1; ns-1800.awsdns-33.co.uk directs to 205.251.199.8 and 2600:9000:5307:800::1.

Mail Servers

Five mail servers handle lambda-bio.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

lambda-bio.com shares at least some of its mail servers with other domains — for example coffeeconex.com, retribal.com, growimpacts.com and two more.

It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.

Hosts with two IP numbers each:

aspmx.l.google.com points to 172.217.76.27 and 2a00:1450:4009:c0f::1b.

alt1.aspmx.l.google.com points to 142.250.102.27 and 2a00:1450:4025:402::1b.

alt2.aspmx.l.google.com points to 192.178.213.26 and 2a00:1450:4013:c1e::1b.

alt3.aspmx.l.google.com points to 142.251.127.27 and 2a00:1450:4001:c21::1b.

alt4.aspmx.l.google.com points to 172.253.148.27 and 2a00:1450:4025:4401::1b.