Skip to content
https://pair.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.pair.com/
200https://pair.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://pair.com/ https://pair.com/

Consistent

B
TLS Certificate Expiry & Recommendations
269 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

269
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
2 A records, 115 ms lookup
PASS
2 A records, 115 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.34.254, 172.67.210.110
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3032::ac43:d26e, 2606:4700:3031::6815:22fe
Info::
2 nameserver(s) configured
Got: pdns0.pit.pair.net, pdns0.den.pair.net
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 115 ms
Got: 115 ms
A104.21.34.254, 172.67.210.110
AAAA2606:4700:3032::ac43:d26e, 2606:4700:3031::6815:22fe
CNAME
NSpdns0.pit.pair.net, pdns0.den.pair.net
MX
100 mx.pair.com
TXT
SPF v=spf1 include:spf1.pair.com include:spf2.pair.com include:spf3.pair.com include...
google-site-verification=5p3cbg0QyFuBi01xFTMD8tauXHUo9Iz-6_4b0eKJUh0
google-site-verification=NHq-UmX3wzmEb3NStM3-7hqiTDZaugG6Yn_aNgaQ9KU
google-site-verification=hayOo9URMjEW9WXWl0qmuSwRQigwSZGkfaZQaV64hnQ
google-site-verification=oGFRbz0jXuyLfeZ8DdOy-DQmjpPgQQS6TP-UZicJP8g
BunnyTicket340650
CAALookup not available with standard resolver
Resolved in 115 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 979 ms total
PASS
1 redirect(s), 979 ms total
Info::
Single redirect
Got: https://pair.com → https://www.pair.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 979 ms total
Got: 979 ms

https://pair.com

416 ms · HTTP/1.1

301

https://www.pair.com/

563 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pair.com301416 msHTTP/1.1cloudflare
2https://www.pair.com/200563 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3032::ac43:d26e, 2606:4700:3031::6815:22fe
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3032::ac43:d26e, 2606:4700:3031::6815:22fe Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 204 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 204 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow: /wp-json/
Disallow: /?rest_route=

Sitemap: https://www.pair.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
A+
Domain Intelligence
pair.com — via pair Networks, Inc. d/b/a pair Domains, 31 years, 1 months old
PASS
pair.com — via pair Networks, Inc. d/b/a pair Domains, 31 years, 1 months old
Info::
Domain registered until Aug 17, 2027 (1 years, 4 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: pair Networks, Inc. d/b/a pair Domains
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Domain expiry

429 days

August 17, 2027

SSL certificate

269 days

Issued by Sectigo Limited

Domain age

31 years, 1 months

Registered August 18, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3032::ac43:d26e

Registrar

pair Networks, Inc. d/b/a pair Domains

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar pair Networks, Inc. d/b/a pair Domains
Created August 18, 1995 (31 years, 1 months ago)
Expires August 17, 2027 (1 years, 4 months)
Last Updated March 1, 2026
Name Servers pdns0.den.pair.net, pdns0.pit.pair.net
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3032::ac43:d26e
Data source: rdap (0.1s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A
HTTP Probe Timing
Total 531 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
113 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
25 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
531 ms
Total Time Total request time from DNS lookup through full response.
531 ms

Connection waterfall

DNS Lookup 113 ms TCP Connect 17 ms TLS Handshake 25 ms Server Processing 376 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f0865065e1b2a12-CDG
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f0865065e1b2a12-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback