questionmark.com - dns.ninja

`questionmark.com`

DNSSEC	🔒 Signed (DS record present)
A	104.21.60.189^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
A	172.67.200.57^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns1-02.azure-dns.com` ⭐
		A	2603:1061:0:700::2^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
		A	13.107.236.2^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
NS	`ns2-02.azure-dns.net`
		A	2620:1ec:8ec:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
		A	150.171.21.2^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
NS	`ns3-02.azure-dns.org`
		A	2a01:111:4000:700::2^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-02.azure-dns.org`
		A	204.14.183.2^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-02.azure-dns.org`
NS	`ns4-02.azure-dns.info`
		A	2620:1ec:bda:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
		A	208.84.5.2^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c27::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadsk-in-f27.1e100.net`
		A	192.179.18.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ry-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 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:c01::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`di-in-f27.1e100.net`
		A	74.125.193.26^{🇺🇸 Google74.125.193.0/24}
			PTR	`di-in-f26.1e100.net`
			PTR	`ig-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	`v=verifydomain MS=ms24725294`
TXT	`v=spf1 a:www.questionmark.com ip4:51.132.249.49 ip4:20.90.87.90 ip4:172.191.1...`
TXT	`google-site-verification=vXFvFJFMkbFo2oIJAZUUeTLSMuseJTEHc3zuo5-7yq0`
TXT	`qmwww.azurewebsites.net`
TXT	`google-site-verification=6HqPeaIjz_aA7gr_bxJDNMVLTHxlsV2CsLYG-MObIl8`
TXT	`access-domain-verification=20c54402adf4ae3d1fbee02fc3999c47ed5a33d41255d9a487...`
TXT	`2969668CE9`
TXT	`plqbm9hnn5nmm0ps77025hvjt6`
TXT	`google-gws-recovery-domain-verification=41415511`
TXT	`proxy-ssl.webflow.com`
TXT	`google-site-verification=mtFaQb-LqCW3O_jgrpi1dATgJYqKSxV7mx_1kQSsyGc`
TXT	`ZOOM_verify_GExT92YY0Um2zEc40miEIl`
TXT	`ca3-3b643ac122244176b3eb8dfeb8425354`
TXT	`35d453eaf017e9bb`
TXT	`atlassian-domain-verification=iwMljHQy4SVeU1y8matcQjN4PHRd3JI8oTuYOHbRMYKaCzd...`
TXT	`slack-domain-verification=0Gae9xR4QhnthnUWI58cKFYpmzlDAyNDyqCEb37U`
TXT	`google-site-verification=hGfyPzoS7aCRpLmYEp4q_utn25mNBeWSaFUUjm1gULg`
TXT	`logmein-verification-code=211a1c56-5561-4b5c-8e5d-b2b8e0b1d171`
TXT	`docusign=ab6afa70-a009-40bb-b644-2ab10424bcf7`
SOA	`ns1-02.azure-dns.com`hostmaster@questionmark.com 2005-09-12 #86

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

rank #181365 globally
rank #75025 in the tld
WOT: SAFE (78/100)
📈 Tranco rank: #245,285

Subdomains

autodiscover.questionmark.com

ondemand.questionmark.com

ftp.questionmark.com

licensing.questionmark.com

Same first word

questionmark.at

questionmark.ru

questionmark.com

questionmark.world

questionmark.eu

questionmark.it

DNS History

21 records (11 active, 10 former)

●NSns1-02.azure-dns.com2018-08-09 → 2026-07-31 · 3 obs

○ 2017-09-30 02:07:12
● 2018-08-09 15:56:26
● 2026-07-31 01:37:04

○NSns1.cervalis.com2015-05-22 → 2017-09-30 · 4 obs

● 2015-05-22 21:53:58
● 2017-09-30 02:07:12
○ 2018-08-09 15:56:26
○ 2026-07-31 01:37:04

●NSns2-02.azure-dns.net2018-08-09 → 2026-07-31 · 3 obs

○ 2017-09-30 02:07:12
● 2018-08-09 15:56:26
● 2026-07-31 01:37:04

○NSns2.cervalis.com2015-05-22 → 2017-09-30 · 4 obs

● 2015-05-22 21:53:58
● 2017-09-30 02:07:12
○ 2018-08-09 15:56:26
○ 2026-07-31 01:37:04

●NSns3-02.azure-dns.org2018-08-09 → 2026-07-31 · 3 obs

○ 2017-09-30 02:07:12
● 2018-08-09 15:56:26
● 2026-07-31 01:37:04

○NSns3.cervalis.com2015-05-22 → 2017-09-30 · 4 obs

● 2015-05-22 21:53:58
● 2017-09-30 02:07:12
○ 2018-08-09 15:56:26
○ 2026-07-31 01:37:04

●NSns4-02.azure-dns.info2018-08-09 → 2026-07-31 · 3 obs

○ 2017-09-30 02:07:12
● 2018-08-09 15:56:26
● 2026-07-31 01:37:04

○NSns4.cervalis.com2015-05-22 → 2017-09-30 · 4 obs

● 2015-05-22 21:53:58
● 2017-09-30 02:07:12
○ 2018-08-09 15:56:26
○ 2026-07-31 01:37:04

○NSns6.cervalis.com2015-10-10 → 2017-09-30 · 5 obs

○ 2015-05-22 21:53:58
● 2015-10-10 20:43:24
● 2017-09-30 02:07:12
○ 2018-08-09 15:56:26
○ 2026-07-31 01:37:04

○NSns7.cervalis.com2015-10-10 → 2017-09-30 · 5 obs

○ 2015-05-22 21:53:58
● 2015-10-10 20:43:24
● 2017-09-30 02:07:12
○ 2018-08-09 15:56:26
○ 2026-07-31 01:37:04

●MXalt1.aspmx.l.google.com2026-02-22 → 2026-07-31 · 3 obs

○ 2018-08-09 15:56:26
● 2026-02-22 11:47:36
● 2026-07-31 01:37:04

●MXalt2.aspmx.l.google.com2026-02-22 → 2026-07-31 · 3 obs

○ 2018-08-09 15:56:26
● 2026-02-22 11:47:36
● 2026-07-31 01:37:04

●MXalt3.aspmx.l.google.com2026-02-22 → 2026-07-31 · 3 obs

○ 2018-08-09 15:56:26
● 2026-02-22 11:47:36
● 2026-07-31 01:37:04

●MXalt4.aspmx.l.google.com2026-02-22 → 2026-07-31 · 3 obs

○ 2018-08-09 15:56:26
● 2026-02-22 11:47:36
● 2026-07-31 01:37:04

●MXaspmx.l.google.com2026-02-22 → 2026-07-31 · 3 obs

○ 2018-08-09 15:56:26
● 2026-02-22 11:47:36
● 2026-07-31 01:37:04

○MXquestionmark-com.mail.eo.outlook.com2015-05-22 → 2018-08-09 · 4 obs

● 2015-05-22 21:53:58
● 2018-08-09 15:56:26
○ 2026-02-22 11:47:36
○ 2026-07-31 01:37:04

●A104.21.60.1892026-07-08 → 2026-07-31 · 3 obs

○ 2026-02-22 11:47:36
● 2026-07-08 22:48:44
● 2026-07-31 01:37:04

○A162.159.134.422026-02-22 → 2026-02-22 · 4 obs

○ 2018-08-09 15:56:26
● 2026-02-22 11:47:36
○ 2026-07-08 22:48:44
○ 2026-07-31 01:37:04

●A172.67.200.572026-07-08 → 2026-07-31 · 3 obs

○ 2026-02-22 11:47:36
● 2026-07-08 22:48:44
● 2026-07-31 01:37:04

○A204.144.121.2072015-05-22 → 2015-05-22 · 3 obs

● 2015-05-22 21:53:58
○ 2015-10-10 20:43:24
○ 2026-07-31 01:37:04

○A23.96.124.252015-10-10 → 2018-08-09 · 5 obs

○ 2015-05-22 21:53:58
● 2015-10-10 20:43:24
● 2018-08-09 15:56:26
○ 2026-02-22 11:47:36
○ 2026-07-31 01:37:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, d.gtld-servers.net, c.gtld-servers.net, j.gtld-servers.net...	-
questionmark.com	ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info	2 records

✅ Authoritative Response

Server:204.14.183.2

NS records: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 369ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.60.189, 172.67.200.57`
NS	4	`ns1-02.azure-dns.com, ns2-02.azure-dns.net...`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	19	`v=verifydomain MS=ms24725294, v=spf1 a:www.questionmark.com ip4:51.132...`
SOA	1	`ns1-02.azure-dns.com hostmaster.question`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-02.azure-dns.com, ns1-02.azure-dns.com)

Analysis

Hierarchy

autodiscover.questionmark.com, ondemand.questionmark.com, ftp.questionmark.com and licensing.questionmark.com each fall under the parent domain questionmark.com.

IP Addresses

questionmark.com resolves to the IP addresses 104.21.60.189 and 172.67.200.57

Two other host names, along with ellingtonmarketing.com, juleslotcuan.id and www.megapolis-online.com, also share IP numbers with questionmark.com.

Name Servers

The NS records for questionmark.com point to four name servers: ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org.

questionmark.com partially shares its NS delegation with several other domains, including hotmanl.com, cts.jcci.or.jp, pilotlegis.com and two others.

ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org each carry two IP addresses. ns1-02.azure-dns.com has 13.107.236.2 and 2603:1061:0:700::2; ns4-02.azure-dns.info has 208.84.5.2 and 2620:1ec:bda:700::2; ns2-02.azure-dns.net has 150.171.21.2 and 2620:1ec:8ec:700::2; ns3-02.azure-dns.org has 204.14.183.2 and 2a01:111:4000:700::2.

Mail Servers

questionmark.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between questionmark.com and other domains, including ns500742.ns500671.ns500671.ns500671.ns500742.ns500704.ns500705.ns500705.ns500705.ns500688.ns500131.lustychickser.com, atalgerie.com, ns500671.ns500742.ns500742.ns500742.ns500704.ns500671.ns500704.ns500671.ns500649.ns500649.ns500649.ns500153.tenderladiesbz.com and two others.

alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.

Host names that have two IP addresses:

The A records for aspmx.l.google.com return 192.179.18.27 and 2607:f8b0:4004:c27::1b.

The A records for alt1.aspmx.l.google.com return 108.177.123.27 and 2800:3f0:4003:c0f::1b.

The A records for alt2.aspmx.l.google.com return 74.125.193.26 and 2a00:1450:400b:c01::1b.

The A records for alt3.aspmx.l.google.com return 192.178.223.26 and 2a00:1450:4009:c0f::1b.

The A records for alt4.aspmx.l.google.com return 172.253.157.27 and 2a00:1450:400c:c23::1a.