🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`layersqueue.com`

DNSSEC	⚠️ Not signed
NS	`maxim.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2cc6^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`maxim.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c3c6^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`maxim.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:23c6^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`maxim.ns.cloudflare.com`
		A	108.162.195.198^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`maxim.ns.cloudflare.com`
		A	162.159.44.198^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`maxim.ns.cloudflare.com`
		A	172.64.35.198^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`maxim.ns.cloudflare.com`
NS	`treasure.ns.cloudflare.com`
		A	2606:4700:50::a29f:2674^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`treasure.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c274^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`treasure.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2274^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`treasure.ns.cloudflare.com`
		A	108.162.194.116^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`treasure.ns.cloudflare.com`
		A	162.159.38.116^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`treasure.ns.cloudflare.com`
		A	172.64.34.116^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`treasure.ns.cloudflare.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f27.1e100.net`
		A	142.250.31.27^{🇺🇸 Google142.250.31.0/24}
			PTR	`bj-in-f27.1e100.net`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c17::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f27.1e100.net`
		A	2607:f8b0:4004:c1f::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f26.1e100.net`
		A	2607:f8b0:4004:c1f::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f27.1e100.net`
		A	2607:f8b0:4004:c21::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pe-in-f26.1e100.net`
		A	64.233.180.26^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-in-f26.1e100.net`
		A	64.233.180.27^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
		A	142.251.16.26^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f26.1e100.net`
		A	142.251.179.26^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f26.1e100.net`
		A	142.251.179.27^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f27.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.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.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	`google-site-verification=MXL7z68hc9K-LsSWbfO6yX7ddpRXTyCvZCFBjBrDQQI`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`maxim.ns.cloudflare.com`dns@cloudflare.com serial=2411543353

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

Same first word

layersqueue.com

Previous names

Next names

DNS History

8 records (8 active, 0 former)

●NSmaxim.ns.cloudflare.com2026-08-15 → 2026-09-12 · 2 obs

● 2026-08-15 01:01:34
● 2026-09-12 15:45:34

●NStreasure.ns.cloudflare.com2026-08-15 → 2026-09-12 · 2 obs

● 2026-08-15 01:01:34
● 2026-09-12 15:45:34

●MXalt1.aspmx.l.google.com2026-08-15 → 2026-09-12 · 2 obs

● 2026-08-15 01:01:34
● 2026-09-12 15:45:34

●MXalt2.aspmx.l.google.com2026-08-15 → 2026-09-12 · 2 obs

● 2026-08-15 01:01:34
● 2026-09-12 15:45:34

●MXalt3.aspmx.l.google.com2026-08-15 → 2026-09-12 · 2 obs

● 2026-08-15 01:01:34
● 2026-09-12 15:45:34

●MXalt4.aspmx.l.google.com2026-08-15 → 2026-09-12 · 2 obs

● 2026-08-15 01:01:34
● 2026-09-12 15:45:34

●MXaspmx.l.google.com2026-08-15 → 2026-09-12 · 2 obs

● 2026-08-15 01:01:34
● 2026-09-12 15:45:34

●MXsmtp.google.com2026-08-15 → 2026-09-12 · 2 obs

● 2026-08-15 01:01:34
● 2026-09-12 15:45:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, h.gtld-servers.net, b.gtld-servers.net, l.gtld-servers.net...	-
layersqueue.com	treasure.ns.cloudflare.com, maxim.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.195.198

NS records: treasure.ns.cloudflare.com, maxim.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for layersqueue.com (unsigned zone)

⏱️ Timing

Total: 533ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`maxim.ns.cloudflare.com, treasure.ns.cloudflare.com`
MX	6	`aspmx.l.google.com (pri: 1), smtp.google.com (pri: 1)...`
TXT	2	`google-site-verification=MXL7z68hc9K-LsS, v=spf1 include:_spf.google.com ~all`
SOA	1	`maxim.ns.cloudflare.com dns.cloudflare.c`

📌 Glue Records Collected

Total: 12

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

Analysis

Name Servers

layersqueue.com uses two name servers for its delegation: maxim.ns.cloudflare.com and treasure.ns.cloudflare.com.

layersqueue.com shares its name server setup with other domains, including dielineco.com, banruo.net, alexglushenko.com and two others.

There is at least partial name server overlap between layersqueue.com and other domains — indowin88jpterpercaya.com, bybitjp.app, igotaslingshot.com and two more among them.

These name servers frequently co-occur with the name servers titan.ns.cloudflare.com and mike.ns.cloudflare.com.

Host names with 6 IP numbers:

Hostname maxim.ns.cloudflare.com directs to 108.162.195.198, 162.159.44.198 and 172.64.35.198 along with 3 other IP addresses.

Hostname treasure.ns.cloudflare.com directs to 108.162.194.116, 162.159.38.116 and 172.64.34.116 along with 3 other IP addresses.

Mail Servers

layersqueue.com accepts email via 6 mail servers: smtp.google.com, aspmx.l.google.com, alt1.aspmx.l.google.com and 3 other.

layersqueue.com shares mail servers — at least in part — with other domains, including gracelandsanford.com, usaflexphase.co, slon.com.tr and two others.

These mail servers are frequently used alongside mail servers alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and 4 other.

Host names with 9 IP numbers:

Hostname smtp.google.com directs to 64.233.180.26, 64.233.180.27 and 142.251.16.26 along with 6 other IP addresses.

Host names with two IP numbers:

aspmx.l.google.com directs traffic to 142.250.31.27 and 2607:f8b0:4004:c1b::1b.

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

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

alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.

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