lambda-one.app - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`lambda-one.app`

DNSSEC	⚠️ Not signed
A	2a09:8280:1::6:842e^{🇺🇸 FLYIO-12a09:8280:1::/48 Proxy Registration / Customer Route}
		PTR	`ipv6.customer.flyio.net`
A	66.241.124.64^{🇺🇸 FLYIO-166.241.124.0/23 Fly.io Edge Network}
NS	`ns1.digitalocean.com` ⭐
		A	2606:4700:52::ac40:34d2^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
		A	172.64.52.210^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
NS	`ns2.digitalocean.com`
		A	2606:4700:5a::ac40:3515^{🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
		A	172.64.53.21^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
NS	`ns3.digitalocean.com`
		A	2606:4700:52::ac40:31d1^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
		A	172.64.49.209^{🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
SOA	`ns1.digitalocean.com`hostmaster@lambda-one.app serial=0

`app`

	DNSSEC	⚠️ Not signed
	NS	`ns-tld1.charlestonroadregistry.com` ⭐
	NS	`ns-tld2.charlestonroadregistry.com`
	NS	`ns-tld3.charlestonroadregistry.com`
	NS	`ns-tld4.charlestonroadregistry.com`
	NS	`ns-tld5.charlestonroadregistry.com`
	SOA	`ns-tld1.charlestonroadregistry.com`cloud-dns-hostmaster@google.com serial=101427

🔒 HSTS Preload (+subdomains)

Same first word

lambda-one.com

lambda-one.app

lambda-one.duckdns.org

Similar names

adam-noble.com

moenda-lab.pages.dev

medan-bola.com

daemon-lab.duckdns.org

Previous names

lamatera.app

lamatna.app

lamatrix.app

lamaz.app

lamazmorra.app

lamb.app

lamb276.app

lamba-bet.app

lamba.app

lambabet.app

lambada.app

lambada777.app

lambadapg.app

lambah.app

lambalia.app

lambangbet.app

lambarde.app

lambari.app

lambchop.app

lambd.app

Next names

DNS History

5 records (5 active, 0 former)

●NSns1.digitalocean.com2026-09-01 → 2026-11-06 · 2 obs

● 2026-09-01 20:03:20
● 2026-11-06 18:42:20

●NSns2.digitalocean.com2026-09-01 → 2026-11-06 · 2 obs

● 2026-09-01 20:03:20
● 2026-11-06 18:42:20

●NSns3.digitalocean.com2026-09-01 → 2026-11-06 · 2 obs

● 2026-09-01 20:03:20
● 2026-11-06 18:42:20

●A2a09:8280:1::6:842e2026-09-01 → 2026-11-06 · 2 obs

● 2026-09-01 20:03:20
● 2026-11-06 18:42:20

●A66.241.124.642026-09-01 → 2026-11-06 · 2 obs

● 2026-09-01 20:03:20
● 2026-11-06 18:42:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
app	ns-tld2.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com...	-
lambda-one.app	ns3.digitalocean.com, ns2.digitalocean.com, ns1.digitalocean.com	-

✅ Authoritative Response

Server:172.64.52.210

NS records: ns3.digitalocean.com, ns2.digitalocean.com, ns1.digitalocean.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for lambda-one.app (unsigned zone)

⏱️ Timing

Total: 874ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`66.241.124.64`
AAAA	1	`2a09:8280:1::6:842e`
NS	3	`ns3.digitalocean.com, ns1.digitalocean.com...`
SOA	1	`ns1.digitalocean.com hostmaster.lambda-o`

Analysis

IP Addresses

lambda-one.app points to the IP addresses 66.241.124.64 and 2a09:8280:1::6:842e

cherrybubbles.com, prossimagara.it, rank.live and two other host names share IP numbers with lambda-one.app.

Name Servers

The authoritative name servers for lambda-one.app are ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com — three in total.

There is at least partial name server overlap between lambda-one.app and other domains — akarsuicecek.com, ioys.lt, thechoirmaster.com and two more among them.

The name servers ns1.tiendanegocio.com, ns2.tiendanegocio.com and ns3.tiendanegocio.com are often found in combination with these name servers.

ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com all resolve to exactly two IP numbers apiece: ns1.digitalocean.com → 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com → 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com → 172.64.49.209 and 2606:4700:52::ac40:31d1.