🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`queueaim.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::6815:53a1^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::ac43:b267^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.83.161^{Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.178.103^{🇺🇸 Cloudflare172.67.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`may.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a87^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`may.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c087^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`may.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2087^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`may.ns.cloudflare.com`
		A	108.162.192.135^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`may.ns.cloudflare.com`
		A	172.64.32.135^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`may.ns.cloudflare.com`
		A	173.245.58.135^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`may.ns.cloudflare.com`
NS	`toby.ns.cloudflare.com`
		A	2606:4700:58::adf5:3bef^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`toby.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1ef^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`toby.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21ef^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`toby.ns.cloudflare.com`
		A	108.162.193.239^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`toby.ns.cloudflare.com`
		A	172.64.33.239^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`toby.ns.cloudflare.com`
		A	173.245.59.239^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`toby.ns.cloudflare.com`
MX	`route2.mx.cloudflare.net` ⭐
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route1.mx.cloudflare.net`⁽⁷³⁾
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽⁹⁷⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.83.161, 172.67.178.103
		IPv6 hints	2606:4700:3030::6815:53a1, 2606:4700:3036::ac43:b267
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=220, name=cloudflare-ech.com
SOA	`may.ns.cloudflare.com`dns@cloudflare.com serial=2410909928

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

Same first word

queueaim.com

Similar names

iamqueue.xyz

Previous names

Next names

DNS History

9 records (9 active, 0 former)

●NSmay.ns.cloudflare.com2026-08-19 → 2026-08-29 · 2 obs

● 2026-08-19 15:56:44
● 2026-08-29 20:27:44

●NStoby.ns.cloudflare.com2026-08-19 → 2026-08-29 · 2 obs

● 2026-08-19 15:56:44
● 2026-08-29 20:27:44

●MXroute1.mx.cloudflare.net2026-08-19 → 2026-08-29 · 2 obs

● 2026-08-19 15:56:44
● 2026-08-29 20:27:44

●MXroute2.mx.cloudflare.net2026-08-19 → 2026-08-29 · 2 obs

● 2026-08-19 15:56:44
● 2026-08-29 20:27:44

●MXroute3.mx.cloudflare.net2026-08-19 → 2026-08-29 · 2 obs

● 2026-08-19 15:56:44
● 2026-08-29 20:27:44

●A104.21.83.1612026-08-19 → 2026-08-29 · 2 obs

● 2026-08-19 15:56:44
● 2026-08-29 20:27:44

●A172.67.178.1032026-08-19 → 2026-08-29 · 2 obs

● 2026-08-19 15:56:44
● 2026-08-29 20:27:44

●A2606:4700:3030::6815:53a12026-08-19 → 2026-08-29 · 2 obs

● 2026-08-19 15:56:44
● 2026-08-29 20:27:44

●A2606:4700:3036::ac43:b2672026-08-19 → 2026-08-29 · 2 obs

● 2026-08-19 15:56:44
● 2026-08-29 20:27:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
queueaim.com	may.ns.cloudflare.com, toby.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.193.239

NS records: may.ns.cloudflare.com, toby.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for queueaim.com (unsigned zone)

⏱️ Timing

Total: 255ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.83.161, 172.67.178.103`
AAAA	2	`2606:4700:3036::ac43:b267, 2606:4700:3030::6815:53a1`
NS	2	`may.ns.cloudflare.com, toby.ns.cloudflare.com`
MX	3	`route2.mx.cloudflare.net (pri: 27), route1.mx.cloudflare.net (pri: 73)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`may.ns.cloudflare.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

queueaim.com points to the four IP addresses 104.21.83.161, 172.67.178.103, 2606:4700:3030::6815:53a1 and 2606:4700:3036::ac43:b267.

Additional host names — dekuna.com, 212010.cn, linetogel992.com and two others — share IP numbers with queueaim.com.

Name Servers

Two name servers handle the delegation for queueaim.com: may.ns.cloudflare.com and toby.ns.cloudflare.com.

queueaim.com shares its name server setup with other domains, including tyy98.xyz, qwhjq.com, dataportal.nz and two others.

There is at least partial name server overlap between queueaim.com and other domains — zheyqaq.workers.dev, mykyon.com, abol-pormalat.workers.dev and two more among them.

The name servers hope.ns.cloudflare.com, ollie.ns.cloudflare.com and brady.ns.cloudflare.com are often found in combination with these name servers.

Host names with 6 IP numbers:

may.ns.cloudflare.com resolves to 108.162.192.135, 172.64.32.135 and 173.245.58.135 among others, with 3 other IP addresses in total.

toby.ns.cloudflare.com resolves to 108.162.193.239, 172.64.33.239 and 173.245.59.239 among others, with 3 other IP addresses in total.

Mail Servers

Incoming mail for queueaim.com is delivered via three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

queueaim.com shares mail servers — at least in part — with other domains, including ihsanlabs.my.id, gh2c.net, neputa-note.net and two others.

Host names with 6 IP numbers:

route1.mx.cloudflare.net resolves to 162.159.205.11, 162.159.205.12 and 162.159.205.13 among others, with 3 other IP addresses in total.

route2.mx.cloudflare.net resolves to 162.159.205.17, 162.159.205.18 and 162.159.205.19 among others, with 3 other IP addresses in total.

route3.mx.cloudflare.net resolves to 162.159.205.23, 162.159.205.24 and 162.159.205.25 among others, with 3 other IP addresses in total.

queueaim.com - robtex.com

queueaim.com

com

Same first word

Similar names

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`queueaim.com`

`com`