queuesense.com - dns.ninja

`queuesense.com`

DNSSEC	⚠️ Not signed
A	192.0.78.24^{🇺🇸 Automattic192.0.78.0/24 Route Object}
A	192.0.78.25^{🇺🇸 Automattic192.0.78.0/24 Route Object}
NS	`ns1.wordpress.com` ⭐
		A	2a04:fa87:ffff::c6b5:7409^{🇮🇪 Automattic2a04:fa87:ffff::/48}
			PTR	`ns1.wordpress.com`
		A	198.181.116.9^{🇺🇸 Automattic198.181.116.0/24 Route Object}
			PTR	`ns1.wordpress.com`
NS	`ns2.wordpress.com`
		A	2a04:fa87:ffff::c6b5:7509^{🇮🇪 Automattic2a04:fa87:ffff::/48}
			PTR	`ns2.wordpress.com`
		A	198.181.117.9^{🇺🇸 Automattic198.181.117.0/24 Route Object}
			PTR	`ns2.wordpress.com`
NS	`ns3.wordpress.com`
		A	2620:115:c00f::c000:4a09^{🇺🇸 Automattic2620:115:c00f::/48 Route6 Object}
			PTR	`ns3.wordpress.com`
		A	192.0.74.9^{🇺🇸 Automattic192.0.74.0/24 Route Object}
			PTR	`ns3.wordpress.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c17::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f27.1e100.net`
		A	172.253.115.27^{🇺🇸 Google172.253.115.0/24}
			PTR	`bg-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-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.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.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.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.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	`google-site-verification=SvkriOgp0r2IiUgj9o4wzRQ4DVH_5wzgREvYm4C1E2s`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns1.wordpress.com`hostmaster@wordpress.com 2005-07-18 #58

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

Same first word

queuesense.com

DNS History

18 records (10 active, 8 former)

○NSdns1.registrar-servers.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 04:33:30
○ 2026-04-01 17:47:38
○ 2026-07-10 07:11:36

○NSdns2.registrar-servers.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 04:33:30
○ 2026-04-01 17:47:38
○ 2026-07-10 07:11:36

●NSns1.wordpress.com2026-04-01 → 2026-07-10 · 3 obs

○ 2017-05-09 04:33:30
● 2026-04-01 17:47:38
● 2026-07-10 07:11:36

●NSns2.wordpress.com2026-04-01 → 2026-07-10 · 3 obs

○ 2017-05-09 04:33:30
● 2026-04-01 17:47:38
● 2026-07-10 07:11:36

●NSns3.wordpress.com2026-04-01 → 2026-07-10 · 3 obs

○ 2017-05-09 04:33:30
● 2026-04-01 17:47:38
● 2026-07-10 07:11:36

●MXalt1.aspmx.l.google.com2026-04-01 → 2026-07-10 · 3 obs

○ 2017-05-09 04:33:30
● 2026-04-01 17:47:38
● 2026-07-10 07:11:36

●MXalt2.aspmx.l.google.com2026-04-01 → 2026-07-10 · 3 obs

○ 2017-05-09 04:33:30
● 2026-04-01 17:47:38
● 2026-07-10 07:11:36

●MXalt3.aspmx.l.google.com2026-04-01 → 2026-07-10 · 3 obs

○ 2017-05-09 04:33:30
● 2026-04-01 17:47:38
● 2026-07-10 07:11:36

●MXalt4.aspmx.l.google.com2026-04-01 → 2026-07-10 · 3 obs

○ 2017-05-09 04:33:30
● 2026-04-01 17:47:38
● 2026-07-10 07:11:36

●MXaspmx.l.google.com2026-04-01 → 2026-07-10 · 3 obs

○ 2017-05-09 04:33:30
● 2026-04-01 17:47:38
● 2026-07-10 07:11:36

○MXeforward1.registrar-servers.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 04:33:30
○ 2026-04-01 17:47:38
○ 2026-07-10 07:11:36

○MXeforward2.registrar-servers.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 04:33:30
○ 2026-04-01 17:47:38
○ 2026-07-10 07:11:36

○MXeforward3.registrar-servers.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 04:33:30
○ 2026-04-01 17:47:38
○ 2026-07-10 07:11:36

○MXeforward4.registrar-servers.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 04:33:30
○ 2026-04-01 17:47:38
○ 2026-07-10 07:11:36

○MXeforward5.registrar-servers.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 04:33:30
○ 2026-04-01 17:47:38
○ 2026-07-10 07:11:36

●A192.0.78.242026-04-01 → 2026-07-10 · 3 obs

○ 2017-05-09 04:33:30
● 2026-04-01 17:47:38
● 2026-07-10 07:11:36

●A192.0.78.252026-04-01 → 2026-07-10 · 3 obs

○ 2017-05-09 04:33:30
● 2026-04-01 17:47:38
● 2026-07-10 07:11:36

○A192.64.119.1902017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 04:33:30
○ 2026-04-01 17:47:38
○ 2026-07-10 07:11:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
queuesense.com	ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com	6 records

✅ Authoritative Response

Server:198.181.116.9

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for queuesense.com (unsigned zone)

⏱️ Timing

Total: 190ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`192.0.78.25, 192.0.78.24`
NS	3	`ns2.wordpress.com, ns3.wordpress.com...`
MX	5	`alt1.aspmx.l.google.com (pri: 5), alt3.aspmx.l.google.com (pri: 10)...`
TXT	2	`google-site-verification=SvkriOgp0r2IiUg, v=spf1 include:_spf.google.com ~all`
SOA	1	`ns1.wordpress.com hostmaster.wordpress.c`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns1.wordpress.com, ns1.wordpress.com, ns2.wordpress.com...)

Analysis

IP Addresses

queuesense.com has two IP addresses: 192.0.78.24 and 192.0.78.25

catherinaboh.com, bilust.com, cemkarayalcin.com and two other host names share IP numbers with queuesense.com.

Name Servers

The authoritative name servers for queuesense.com are ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com — three in total.

The name servers of queuesense.com overlap at least partially with those of other domains — among them rollingprose.com, californiagirlsproductions.com, boulimie-hyperphagie.com and two more.

ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com all resolve to exactly two IP numbers apiece: ns1.wordpress.com → 198.181.116.9 and 2a04:fa87:ffff::c6b5:7409; ns2.wordpress.com → 198.181.117.9 and 2a04:fa87:ffff::c6b5:7509; ns3.wordpress.com → 192.0.74.9 and 2620:115:c00f::c000:4a09.

Mail Servers

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

queuesense.com has at least partial mail server overlap with other domains such as aclinstitute.com, shaheengroup.me, tedxlondon.com and two more.

These mail servers commonly co-occur with mail servers alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com directs traffic to 172.253.115.27 and 2607:f8b0:4004:c17::1b.

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

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

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

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