🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`lambdaplugin.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::6815:57ae^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::ac43:aa7a^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.87.174^{Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.170.122^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`lindsey.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:2605^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lindsey.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c205^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`lindsey.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2205^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`lindsey.ns.cloudflare.com`
		A	108.162.194.5^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lindsey.ns.cloudflare.com`
		A	162.159.38.5^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lindsey.ns.cloudflare.com`
		A	172.64.34.5^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lindsey.ns.cloudflare.com`
NS	`wells.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c7d^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`wells.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c37d^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`wells.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:237d^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`wells.ns.cloudflare.com`
		A	108.162.195.125^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`wells.ns.cloudflare.com`
		A	162.159.44.125^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`wells.ns.cloudflare.com`
		A	172.64.35.125^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`wells.ns.cloudflare.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c06::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bg-in-f27.1e100.net`
		A	142.251.179.26^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 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.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2607:f8b0:4001:c79::1b^{🇺🇸 Google2607:f8b0:4001::/48}
			PTR	`yucbfwv-in-f27.1e100.net`
		A	173.194.42.27^{🇺🇸 Google173.194.0.0/16}
			PTR	`yucbfwv-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 mx ip4:77.36.4.48 ip4:77.36.4.49 ip4:77.36.4.50 ip4:77.36.4.51 -all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.87.174, 172.67.170.122
		IPv6 hints	2606:4700:3031::6815:57ae, 2606:4700:3036::ac43:aa7a
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=105, name=cloudflare-ech.com
SOA	`lindsey.ns.cloudflare.com`dns@cloudflare.com serial=2417947105

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

Same first word

lambdaplugin.com

Similar names

pluginlambda.com

Previous names

Next names

DNS History

24 records (11 active, 13 former)

●NSlindsey.ns.cloudflare.com2026-09-01 → 2026-11-09 · 3 obs

○ 2017-02-11 15:05:46
● 2026-09-01 15:31:20
● 2026-11-09 19:46:08

○NSns.parktons.com2016-06-20 → 2016-06-20 · 4 obs

○ 2016-03-04 10:50:52
● 2016-06-20 17:25:02
○ 2017-02-11 15:05:46
○ 2026-11-09 19:46:08

○NSns1.thinline.cz2015-07-15 → 2016-03-04 · 4 obs

● 2015-07-15 21:14:58
● 2016-03-04 10:50:52
○ 2016-06-20 17:25:02
○ 2026-11-09 19:46:08

○NSns2.parktons.com2016-06-20 → 2016-06-20 · 4 obs

○ 2016-03-04 10:50:52
● 2016-06-20 17:25:02
○ 2017-02-11 15:05:46
○ 2026-11-09 19:46:08

○NSns2.thinline.cz2015-07-15 → 2016-03-04 · 4 obs

● 2015-07-15 21:14:58
● 2016-03-04 10:50:52
○ 2016-06-20 17:25:02
○ 2026-11-09 19:46:08

○NSns3.cesky-hosting.eu2015-07-15 → 2016-03-04 · 4 obs

● 2015-07-15 21:14:58
● 2016-03-04 10:50:52
○ 2016-06-20 17:25:02
○ 2026-11-09 19:46:08

●NSwells.ns.cloudflare.com2026-09-01 → 2026-11-09 · 3 obs

○ 2017-02-11 15:05:46
● 2026-09-01 15:31:20
● 2026-11-09 19:46:08

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

○ 2017-02-11 15:05:46
● 2026-09-01 15:31:20
● 2026-11-09 19:46:08

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

○ 2017-02-11 15:05:46
● 2026-09-01 15:31:20
● 2026-11-09 19:46:08

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

○ 2017-02-11 15:05:46
● 2026-09-01 15:31:20
● 2026-11-09 19:46:08

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

○ 2017-02-11 15:05:46
● 2026-09-01 15:31:20
● 2026-11-09 19:46:08

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

○ 2017-02-11 15:05:46
● 2026-09-01 15:31:20
● 2026-11-09 19:46:08

○MXmail.user-mail.net2016-06-20 → 2016-06-20 · 3 obs

● 2016-06-20 17:25:02
○ 2017-02-11 15:05:46
○ 2026-11-09 19:46:08

●A104.21.87.1742026-09-07 → 2026-11-09 · 5 obs

○ 2026-09-01 15:31:20
● 2026-09-07 21:18:24
○ 2026-09-12 03:52:58
● 2026-10-10 10:57:40
● 2026-11-09 19:46:08

●A172.67.170.1222026-09-07 → 2026-11-09 · 5 obs

○ 2026-09-01 15:31:20
● 2026-09-07 21:18:24
○ 2026-09-12 03:52:58
● 2026-10-10 10:57:40
● 2026-11-09 19:46:08

○A185.28.193.1922016-06-20 → 2016-06-20 · 4 obs

○ 2016-03-04 10:50:52
● 2016-06-20 17:25:02
○ 2017-02-11 15:05:46
○ 2026-11-09 19:46:08

○A185.31.18.1332015-07-15 → 2016-03-04 · 4 obs

● 2015-07-15 21:14:58
● 2016-03-04 10:50:52
○ 2016-06-20 17:25:02
○ 2026-11-09 19:46:08

○A188.114.96.02026-09-01 → 2026-09-12 · 6 obs

○ 2017-02-11 15:05:46
● 2026-09-01 15:31:20
○ 2026-09-07 21:18:24
● 2026-09-12 03:52:58
○ 2026-10-10 10:57:40
○ 2026-11-09 19:46:08

○A188.114.97.02026-09-01 → 2026-09-12 · 6 obs

○ 2017-02-11 15:05:46
● 2026-09-01 15:31:20
○ 2026-09-07 21:18:24
● 2026-09-12 03:52:58
○ 2026-10-10 10:57:40
○ 2026-11-09 19:46:08

●A2606:4700:3031::6815:57ae2026-09-07 → 2026-11-09 · 5 obs

○ 2026-09-01 15:31:20
● 2026-09-07 21:18:24
○ 2026-09-12 03:52:58
● 2026-10-10 10:57:40
● 2026-11-09 19:46:08

●A2606:4700:3036::ac43:aa7a2026-09-07 → 2026-11-09 · 5 obs

○ 2026-09-01 15:31:20
● 2026-09-07 21:18:24
○ 2026-09-12 03:52:58
● 2026-10-10 10:57:40
● 2026-11-09 19:46:08

○A2a06:98c1:3120::2026-09-01 → 2026-09-12 · 6 obs

○ 2017-02-11 15:05:46
● 2026-09-01 15:31:20
○ 2026-09-07 21:18:24
● 2026-09-12 03:52:58
○ 2026-10-10 10:57:40
○ 2026-11-09 19:46:08

○A2a06:98c1:3121::2026-09-01 → 2026-09-12 · 6 obs

○ 2017-02-11 15:05:46
● 2026-09-01 15:31:20
○ 2026-09-07 21:18:24
● 2026-09-12 03:52:58
○ 2026-10-10 10:57:40
○ 2026-11-09 19:46:08

○A31.170.178.1792016-06-20 → 2016-06-20 · 4 obs

○ 2016-03-04 10:50:52
● 2016-06-20 17:25:02
○ 2017-02-11 15:05:46
○ 2026-11-09 19:46:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
lambdaplugin.com	lindsey.ns.cloudflare.com, wells.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.195.125

NS records: lindsey.ns.cloudflare.com, wells.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)

⏱️ Timing

Total: 101ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.87.174, 172.67.170.122`
AAAA	2	`2606:4700:3036::ac43:aa7a, 2606:4700:3031::6815:57ae`
NS	2	`lindsey.ns.cloudflare.com, wells.ns.cloudflare.com`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	1	`v=spf1 mx ip4:77.36.4.48 ip4:77.36.4.49`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`lindsey.ns.cloudflare.com dns.cloudflare`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (lindsey.ns.cloudflare.com, lindsey.ns.cloudflare.com, lindsey.ns.cloudflare.com...)

Analysis

IP Addresses

lambdaplugin.com directs to four IP numbers, which are 104.21.87.174, 172.67.170.122, 2606:4700:3031::6815:57ae and 2606:4700:3036::ac43:aa7a.

heatassessment.org, habanero88.id, jumanjipetstore.com and two other host names share IP numbers with lambdaplugin.com.

Name Servers

lambdaplugin.com uses two name servers for its delegation: lindsey.ns.cloudflare.com and wells.ns.cloudflare.com.

lambdaplugin.com uses the same name servers as several other domains — among them pafikadipaten.org, www.nordnetz.com, thequickfusion.com and two more.

There is at least partial name server overlap between lambdaplugin.com and other domains — alexandrospeppas95.workers.dev, itagiyuf.com, goldpunt365.com and two more among them.

The name servers janet.ns.cloudflare.com, titan.ns.cloudflare.com and luke.ns.cloudflare.com are often found in combination with these name servers.

Hostnames that resolve to 6 IP addresses:

Hostname lindsey.ns.cloudflare.com directs to 108.162.194.5, 162.159.38.5 and 172.64.34.5 along with 3 other IP addresses.

Hostname wells.ns.cloudflare.com directs to 108.162.195.125, 162.159.44.125 and 172.64.35.125 along with 3 other IP addresses.

Mail Servers

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

lambdaplugin.com has at least partial mail server overlap with other domains such as fluxtelecom.com, antayperu.com, fairfaxridgeanimalhospitalva.com and two more.

These mail servers commonly appear together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and two other mail servers.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com directs traffic to 142.251.179.26 and 2607:f8b0:4004:c06::1b.

alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.

alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com directs traffic to 173.194.42.27 and 2607:f8b0:4001:c79::1b.

alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1a.