pki.goog

We performed a comprehensive analysis of pki.goog on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 447ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 13 KB. Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted. The security headers analysis reveals a score of 15/100 (poor). The following security headers are properly configured: X-Content-Type-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, Referrer-Policy, and Permissions-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 4 technologies across 4 categories powering pki.goog. The detected stack includes Google Analytics 4, Google Tag Manager, reCAPTCHA v3, and Google Fonts. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, pki.goog receives an overall trust score of 63/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, pki.goog receives a trust score of 63/100, which places it in the "Likely Safe" category. This score is calculated by evaluating multiple factors including SSL certificate validity, domain registration history, email authentication protocols, security header configuration, and blacklist status across major threat intelligence databases. The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, and DNSSEC providing authenticated DNS responses. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), missing Referrer-Policy, potentially leaking URL information to third parties, and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked pki.goog against 8 major blacklist databases including Google Safe Browsing, Phishtank, Urlhaus, Openphish, Dnsfilter, Spamhaus Dbl, Surbl, and Virustotal. The domain passed all 8 checks with a clean status, meaning it has not been flagged for phishing, malware distribution, spam, or other malicious activities by any of the tested threat intelligence providers.

Our technology detection engine scanned pki.goog and identified 4 distinct technologies across 4 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for pki.goog. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for pki.goog. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for pki.goog. Fonts: Google Fonts — delivers web fonts for typography for pki.goog. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-JCEW5SPNPE and Google Tag Manager container GTM-TNCB39C. These IDs can be used to identify other websites operated by the same organization.

pki.goog resolves to the IPv4 address 216.239.32.29 and also supports IPv6 (2001:4860:4802:32::1d), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured. The domain name system is managed by 4 name servers: ns1.zdns.google, ns2.zdns.google, ns3.zdns.google, and ns4.zdns.google. Having 4 name servers provides good redundancy — if one fails, the others can continue serving DNS queries. The choice of name servers often indicates the DNS hosting provider or CDN service being used. Email for pki.goog is handled by Google Workspace with 1 MX records configured: smtp.google.com. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF (Sender Policy Framework) is configured, which specifies which mail servers are authorized to send email on behalf of this domain. This helps prevent email spoofing and improves email deliverability. DMARC (Domain-based Message Authentication, Reporting and Conformance) is configured with a reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is enabled for pki.goog, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites. Our subdomain enumeration scan discovered 25 active subdomains for pki.goog: admin.pki.goog, api.pki.goog, app.pki.goog, apps.pki.goog, blog.pki.goog, cdn.pki.goog, community.pki.goog, and dev.pki.goog. Plus 17 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The title tag for pki.goog is good at 28 characters: "Google Trust Services | Home". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 21 characters (acceptable): "Google Trust Services". Google typically displays up to 155-160 characters of the meta description in search results. A compelling meta description with a clear call-to-action can significantly improve click-through rates from search results. The canonical url is correctly set to https://pki.goog/, preventing duplicate content issues, the page language is declared as en, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to pki.goog on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing.