Skip to content
https://pki.goog

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
97
GRADE
A+
FIX
1
REVIEW
1
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
7 PASS 1 REVIEW 1 FIX
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
TLS Certificate Expiry & Recommendations
66 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 55 ms lookup
PASS
1 A records, 55 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 216.239.32.29
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2001:4860:4802:32::1d
Info::
4 nameserver(s) configured
Got: ns1.zdns.google, ns3.zdns.google, ns4.zdns.google, ns2.zdns.google
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: 55 ms
Got: 55 ms
A216.239.32.29
AAAA2001:4860:4802:32::1d
CNAME
NSns1.zdns.google, ns3.zdns.google, ns4.zdns.google, ns2.zdns.google
MX
5 smtp.google.com
TXT
SPF v=spf1 -all
google-site-verification=bldSOD4em6X-G7MCd9EJUqkBhBcN0Ch9eVi4l-rhHU8
CAALookup not available with standard resolver
Resolved in 55 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://pki.goog

https://pki.goog

72 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pki.goog20072 msHTTP/1.1sffe
A+
IPv6 Readiness
IPv6 reachable (22 ms)
PASS
IPv6 reachable (22 ms)
Info::
IPv6 is configured and reachable at 2001:4860:4802:32::1d
Got: 22 ms connect
IPv6 Ready
AAAA Records 2001:4860:4802:32::1d Connection Reachable (22 ms)
A+
Crawlability
robots.txt present, sitemap with 7 URLs
PASS
robots.txt present, sitemap with 7 URLs
Info::
robots.txt is present
Got: 69 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 69 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /ccadb/
Sitemap: https://pki.goog/sitemap.xml
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.pki.goog/
200https://pki.goog/

Preferred variant: non-www

HTTP → HTTPS

301http://pki.goog/ https://pki.goog/

Consistent

A
Domain Intelligence
pki.goog — via MarkMonitor Inc., 9 years, 11 months old
PASS
pki.goog — via MarkMonitor Inc., 9 years, 11 months old
Warning::
Domain expires in 57 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 13, 2026
Info::
DNSSEC is enabled
Info::
Registrar: MarkMonitor Inc.
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

EXPIRED

June 13, 2026

SSL certificate

66 days

Issued by Google Trust Services

Domain age

9 years, 11 months

Registered June 13, 2016

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2001:4860:4802:32::1d

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created June 13, 2016 (9 years, 11 months ago)
Expires June 13, 2026 (1 months)
Last Updated October 9, 2025
Name Servers ns1.zdns.google, ns2.zdns.google, ns3.zdns.google, ns4.zdns.google
DNSSEC Enabled
Hosting
IP Address 2001:4860:4802:32::1d
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

DNS Lookup 21 ms TCP Connect 22 ms TLS Handshake 24 ms Server Processing 24 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback