Skip to content
https://parspack.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
2
REVIEW
7
PASS
8
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
8 PASS 7 REVIEW 2 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700:3037::6815:1494, 2606:4700:3034::ac43:c124
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:3037::6815:1494]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700:3037::6815:1494, 2606:4700:3034::ac43:c124 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 194.26.195.206: lookup 194.26.195.206: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 194.26.195.203: lookup 194.26.195.203: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3037::6815:1494: lookup 2606:4700:3037::6815:1494: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3034::ac43:c124: lookup 2606:4700:3034::ac43:c124: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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.parspack.com/
200https://parspack.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://parspack.com/ → https://parspack.com/

Consistent

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

Certificate validity

150
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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: connection error, /ping: connection error, /status: connection error.
A+
DNS Records
2 A records, 14 ms lookup
PASS
2 A records, 14 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 194.26.195.206, 194.26.195.203
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3037::6815:1494, 2606:4700:3034::ac43:c124
Info::
3 nameserver(s) configured
Got: ns11.parspack.com, ns10.parspack.com, ns12.parspack.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 14 ms
Got: 14 ms
A194.26.195.206, 194.26.195.203
AAAA2606:4700:3037::6815:1494, 2606:4700:3034::ac43:c124
CNAME—
NSns11.parspack.com, ns10.parspack.com, ns12.parspack.com
MX
5 mx1.parspack.com
10 mx2.parspack.com
TXT
661a4d76ef29f102eff59f5bce53efd9a2364b1439212c3b2ed66de392728f8
google-site-verification=Mp6JhZm83bRYRgtJmhjnsC9XHeJoBH7hAiCtOP9tbnc
SPF v=spf1 ip4:46.102.137.39 ip4:37.58.63.151 ip4:185.110.191.48 ip4:109.122.246.138...
redgemtoken=BmPOEe.html
google-site-verification=rez4QUyaIIhVVdECgI95_MTy4-0r68ENjSP_DAAGUXg
CAALookup not available with standard resolver
Resolved in 14 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 9ms across 3 resolvers (spread 12ms)
PASS
Mean 9ms across 3 resolvers (spread 12ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Quad9: 8ms
Got: 8ms via 9.9.9.9:53
Info::
Google: 16ms
Got: 16ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://parspack.com

https://parspack.com

575 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://parspack.com200575 msHTTP/1.1WCDN 3.8.6
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 301 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 301 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Allow: /wp-content/uploads/
Allow: /new/wp-content/
Disallow: /en/*
Disallow: /blg*
Disallow: /new/*
Disallow: /testheaders.php
Disallow: /st/*
Disallow: /*/comment-page-*

###sitemap###
Sitemap: https://parspack.com/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
parspack.com — via Key-Systems GmbH, 17 years, 3 months old, hosted on BitCommand - BitCommand LLC, AM
PASS
parspack.com — via Key-Systems GmbH, 17 years, 3 months old, hosted on BitCommand - BitCommand LLC, AM
Info::
Domain registered until Jun 28, 2028 (2 years 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: Key-Systems GmbH
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.
Info::
Hosting: BitCommand - BitCommand LLC, AM
Got: AS202269
Domain expiry

717 days

June 28, 2028

SSL certificate

150 days

Issued by Asseco Data Systems S.A.

Domain age

17 years, 3 months

Registered June 28, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

BitCommand - BitCommand LLC, AM

ASN AS202269

194.26.195.203

Registrar

Key-Systems GmbH

Unlocked 3 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 Key-Systems GmbH
Created June 28, 2009 (17 years, 3 months ago)
Expires June 28, 2028 (2 years)
Last Updated November 30, 2025
Name Servers ns10.parspack.com, ns11.parspack.com, ns12.parspack.com
DNSSEC Not enabled
Hosting
IP Address 194.26.195.203
ASN AS202269 (BitCommand - BitCommand LLC, AM)
Provider BitCommand - BitCommand LLC, AM
Data source: rdap (0.2s)

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 723 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
14 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
140 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
147 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
582 ms
Total Time Total request time from DNS lookup through full response.
724 ms

Connection waterfall

DNS Lookup 14 ms TCP Connect 140 ms TLS Handshake 147 ms Server Processing 281 ms Content Transfer 141 ms
A+
Operational Status Page
Status page detected via status subdomain
PASS
Status page detected via status subdomain
Info::
Status page link found: https://status.parspack.com/?utm_source=parspack&utm_medium=topbar
Got: https://status.parspack.com/?utm_source=parspack&utm_medium=topbar
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback