`qs3844.pair.com`

CNAME	`vqs3939.pair.com`
DNSSEC	⚠️ Not signed
A	2607:f440::4227:6421^{🇺🇸 AS78592607:f440::/32 Pair Networks, Inc. 2403 Sidney St. STE 210 Pittsburgh, PA 15203}
		PTR	`vqs3939.pair.com`
A	66.39.100.33^{🇺🇸 AS785966.39.0.0/17 Pair Networks, Inc. 2403 Sidney St. STE 210 Pittsburgh, PA 15203}
MX	`vqs3939.pair.com` ⭐
		A	2607:f440::4227:6421^{🇺🇸 AS78592607:f440::/32 Pair Networks, Inc. 2403 Sidney St. STE 210 Pittsburgh, PA 15203}
			PTR	`vqs3939.pair.com`
		A	66.39.100.33^{🇺🇸 AS785966.39.0.0/17 Pair Networks, Inc. 2403 Sidney St. STE 210 Pittsburgh, PA 15203}
			PTR	`vqs3939.pair.com`
TXT	`v=spf1 a -all`

`pair.com`

	DNSSEC	⚠️ Not signed
	A	2606:4700:3031::6815:22fe^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
	A	2606:4700:3032::ac43:d26e^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
	A	104.21.34.254^{Cloudflare104.21.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
	A	172.67.210.110^{🇺🇸 Cloudflare172.67.208.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
	NS	`ns1.pair.com` ⭐
	NS	`pdns0.den.pair.net`
	NS	`pdns0.pit.pair.net`
	MX	`mx.pair.com` ⭐
	TXT	`google-site-verification=5p3cbg0QyFuBi01xFTMD8tauXHUo9Iz-6_4b0eKJUh0`
	TXT	`google-site-verification=oGFRbz0jXuyLfeZ8DdOy-DQmjpPgQQS6TP-UZicJP8g`
	TXT	`google-site-verification=NHq-UmX3wzmEb3NStM3-7hqiTDZaugG6Yn_aNgaQ9KU`
	TXT	`v=spf1 include:spf1.pair.com include:spf2.pair.com include:spf3.pair.com incl...`
	TXT	`google-site-verification=hayOo9URMjEW9WXWl0qmuSwRQigwSZGkfaZQaV64hnQ`
	TXT	`BunnyTicket340650`
	SOA	`ns1.pair.com`root@pair.com 2024-02-14 #53

WOT: SAFE (82/100)
rank #5053 globally
rank #2518 in the tld
WOT: SAFE (83/100)
📈 Tranco rank: #6,863

PTR for

37.2.92.216.in-addr.arpa

5.2.2.0.c.5.8.d.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.4.4.f.7.0.6.2.ip6.arpa

Previously MX for

DNS History

3 records (1 active, 2 former)

○MXqs3844.pair.com2015-05-19 → 2016-12-30 · 4 obs

● 2015-05-19 18:16:42
● 2016-12-30 00:14:32
○ 2026-03-08 13:07:34
○ 2026-03-26 04:17:56

○A216.92.2.372015-05-19 → 2016-12-30 · 4 obs

● 2015-05-19 18:16:42
● 2016-12-30 00:14:32
○ 2026-03-08 13:07:34
○ 2026-03-26 04:17:56

●CNAMEvqs3939.pair.com2026-03-26 → 2026-03-26 · 2 obs

○ 2026-03-08 13:07:34
● 2026-03-26 04:17:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
pair.com	pdns0.pit.pair.net, pdns0.den.pair.net	-

✅ Authoritative Response

Server:216.146.198.35

NS records: pdns0.pit.pair.net, pdns0.den.pair.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for pair.com (unsigned zone)

⏱️ Timing

Total: 330ms | Queries: -

📄 Records

Type	Count	Sample Data
CNAME	1	`vqs3939.pair.com`

Analysis

IP Addresses

qs3844.pair.com has two IP numbers: 2607:f440::4227:6421 and 66.39.100.33.

Other host names, for example vqs3939.pair.com, share IP numbers with qs3844.pair.com.

Mail Servers

A single mail server handles qs3844.pair.com, vqs3939.pair.com.

qs3844.pair.com shares the same mail server setup as other domains, for instance torontomontreallille.org, chiropratiquesportive.com, grafcom.ca, vqs3939.pair.com and carolebrisson.com.

The host name vqs3939.pair.com resolves to two IP numbers: 2607:f440::4227:6421 and 66.39.100.33.

qs3844.pair.com - robtex.com

qs3844.pair.com

pair.com