Is pki.goog Safe? Security Score 86.7/100 | CyStack
Security Overview and Attack Surface Assessment of pki.goog
Google Trust Services | Home
Google Trust Services
United StatesComputers, Electronics and Technology / Computer SecurityGlobal rank #549,606Rank in United States #461,397
Assessed Scan duration: 24sResult from the most recent scan
B86.7/100
Security level
Good
Data confidenceHigh
Scope checked92.9%
A higher score means more observable Internet-facing protections were recorded; it is not proof that the website is legitimate, entirely safe, or free of vulnerabilities.
Is pki.goog safe?
The first priority is “Allowed browser content (CSP)”; review its evidence and recommendation before moving to lower-impact items. The provisional score is 86.7/100 with 92.9% coverage. It reflects only the parts of the attack surface with sufficient evidence.
Does pki.goog show known scam, phishing, or malware signals?
Across 5 checked network reputation sources, CyStack did not find pki.goog or related infrastructure on a warning list. This does not verify the organization, its business practices, or guarantee that the website is completely safe.
The three issues to address first because they have the greatest security impact.
3/3
01Allowed browser content (CSP)This check found a security issue.High
Check result
This check found a security issue.
Why it matters
Content Security Policy (CSP) limits where scripts, styles, frames, and other browser content may come from. A strong policy reduces the impact if an attacker manages to inject content into a page.
What to do
Define only the sources the application needs, test the policy before activating it, and avoid broad wildcard (*) rules, unsafe-inline, and unsafe-eval where possible.
Compare the security level of each area at a glance.
Higher category scores are better. Red means higher risk; gray means there is not enough data to conclude.
Network attack surface95.5/100 · Good100% of this category was checked
Web security50/100 · Review100% of this category was checked
Evidence in this report
What affects the security of pki.goog?
A valid SSL certificate alone does not prove that pki.goog is safe or legitimate. For a fuller picture, this report also checks scam, phishing, and malware signals, exposed email records, IPs and open ports, subdomains, technologies, and CVEs that may apply to detected versions.
Does pki.goog use HTTPS, and is its SSL certificate valid?
pki.goog presented a valid HTTPS certificate at assessment time, valid until September 21, 2026. This status can change when the certificate or server configuration is updated.
Have @pki.goog email addresses appeared in data leak or infostealer records?
No record associated with an @pki.goog email address was found in the currently available data. This does not rule out incidents that have not been observed.
Data sources and scope
Powered by CyStack security monitoring systems
This scan result is compiled from CyStack's cybersecurity monitoring systems, including CyStack VulnScan and CyStack Threat Intelligence, together with publicly available Internet data. The assessment only observes and analyzes information already available; it does not attempt unauthorized access, test passwords, send exploit code, or change or disrupt your systems.
Public-data analysisNo attacks or vulnerability exploitationNo system changes or disruption
CyStack VulnScan for enterprises
A quick check is the first step; risks need continuous monitoring
CyStack VulnScan helps security teams automatically find Internet assets, scan external and internal systems, validate vulnerabilities and track remediation across the organization.
02Protection from deceptive framing (clickjacking)This check found a security issue.Medium
Check result
This check found a security issue.
Why it matters
Another website can place this page inside a hidden or misleading frame and trick a user into clicking an unintended action. Frame restrictions tell browsers which sites, if any, may embed the page.
What to do
Set frame-ancestors in CSP to the required trusted sites, and keep X-Frame-Options for older browsers when appropriate.
03HSTS availabilityThe HTTPS response does not contain an effective HSTS policy.Medium
Check result
The HTTPS response does not contain an effective HSTS policy.
Why it matters
HTTP Strict Transport Security (HSTS) tells a browser to use HTTPS automatically on future visits. This reduces the chance that a visitor is downgraded to an unencrypted connection.
What to do
After confirming that every required page works over HTTPS, send the Strict-Transport-Security header on all HTTPS responses.
Recorded data
Configured:
No
Valid:
No
Transport encryption91.9/100 · Good100% of this category was checked
Threat reputation100/100 · Good100% of this category was checked
Vulnerability and technology risk100/100 · Not enough data28.6% of this category was checked
Email authentication100/100 · Good100% of this category was checked
Data exposure100/100 · Good100% of this category was checked
Domain and DNS hygiene100/100 · Good100% of this category was checked
Issues to review
The complete list of issues to review, including the three priorities highlighted in the summary.
Content Security Policy (CSP) limits where scripts, styles, frames, and other browser content may come from. A strong policy reduces the impact if an attacker manages to inject content into a page.
What to do
Define only the sources the application needs, test the policy before activating it, and avoid broad wildcard (*) rules, unsafe-inline, and unsafe-eval where possible.
Protection from deceptive framing (clickjacking)Website protectionFailed
Check result
This check found a security issue.
Why it matters
Another website can place this page inside a hidden or misleading frame and trick a user into clicking an unintended action. Frame restrictions tell browsers which sites, if any, may embed the page.
What to do
Set frame-ancestors in CSP to the required trusted sites, and keep X-Frame-Options for older browsers when appropriate.
The HTTPS response does not contain an effective HSTS policy.
Why it matters
HTTP Strict Transport Security (HSTS) tells a browser to use HTTPS automatically on future visits. This reduces the chance that a visitor is downgraded to an unencrypted connection.
What to do
After confirming that every required page works over HTTPS, send the Strict-Transport-Security header on all HTTPS responses.
Permissions-Policy controls whether this page and embedded content may use features such as the camera, microphone, and location. Leaving unused features available creates unnecessary access paths.
What to do
Allow each sensitive browser feature only for the pages and trusted origins that require it, and disable the rest.
When a visitor follows a link, the browser may send the previous page's URL to the destination. Paths and query values in that URL can reveal sensitive context to another website.
What to do
Use strict-origin-when-cross-origin or a stricter Referrer-Policy, and avoid placing secrets in URLs.
CyStack confirmed at least 1500 active DNS subdomains. 811 names may expose sensitive services; discovery was partial, so more may exist.
Why it matters
Names containing admin, development, staging, VPN, database, or monitoring terms may point attackers toward valuable systems. A name alone does not prove exposure, but it identifies a surface that should be reviewed.
What to do
Remove obsolete DNS names and protect non-public systems with strong authentication, MFA, network allowlists, or a VPN.
Known-exploited status is inconclusive because the reference data or CVE matching coverage was incomplete.
Why it matters
A possible CVE match also appears in the CISA Known Exploited Vulnerabilities (KEV) catalog, which means attackers have used that vulnerability in real incidents. The match is urgent to investigate, but the installed software still needs to be confirmed as affected.
What to do
Verify the installed product immediately and follow the CISA and vendor instructions for mitigation, patching, or upgrading if it is affected.
Recorded data
Possible vulnerabilities:
0
Candidate Returned:
0
Candidate Total:
0
Complete:
Yes
Potential CVEs for observed versionsSoftware vulnerabilitiesUnknown
Check result
No externally observed exact product version was available for reliable CPE-based lookup.
Why it matters
The detected product and version were compared with vulnerability records from the National Vulnerability Database (NVD). A match is a lead, not confirmation: the installed software may include vendor fixes or may differ from the version visible on the Internet.
What to do
Confirm the exact installed package and read the vendor advisory. If that installation is affected, apply the vendor patch or upgrade to a fixed version.
Recorded data
Possible vulnerabilities:
0
Candidate Returned:
0
Candidate Total:
0
Complete:
Yes
Coverage Warning Candidates:
Other evaluated controls (44)Passed, informational and non-applicable controls are collapsed to keep the report focused.
Blacklist check coverageIP reputationInformation
Check result
5 providers were definitive and 1 were inconclusive.
Why it matters
This shows how many independent blacklist services returned a clear result. A service that was unavailable was not checked successfully and must not be treated as a clean result.
Recorded data
Blocklists with no match:
5
Confirmed blocklist matches:
No
Blocklists checked conclusively:
5
Blocklists unavailable:
1
IPv4 addresses checked:
1
Blocklists reporting an issue:
0
Technologies visible from the InternetSoftware vulnerabilitiesInformation
Check result
Public signals from the website and its open services revealed 5 technology item(s).
Why it matters
Response headers, page content, and other public clues suggest which technologies the service uses. These observations help explain the attack surface, but they can be incomplete or mistaken and do not by themselves confirm a vulnerability.
Recorded data
Technologies found:
5
Detection method:
Website and exposed-service analysis
Root Response Count:
5
Service Inventory Complete:
Yes
Service Inventory Count:
5
Observed WAF, CDN, or edge serviceSoftware vulnerabilitiesInformation
Check result
No WAF, CDN, or edge product matched the passive root-response signals; this does not prove that protection is absent.
Why it matters
Public response details suggest that a Web Application Firewall (WAF), CDN, or other edge service is present. This quick scan identified the provider but did not test whether attack blocking is configured or working correctly.
Observed 0 versioned product(s); 0 had exact CPE mappings and 0 completed lookup(s).
Why it matters
This shows how many detected products had reliable version information and an exact CPE identity, allowing them to be checked against CVE applicability data. A product that could not be checked must not be treated as free of known vulnerabilities.
Recorded data
Possible vulnerabilities:
0
Candidate Returned:
0
Candidate Total:
0
Complete:
Yes
Coverage Warning Candidates:
0
Coverage Warning Count:
0
Certificate matches the websiteHTTPS and encryptionPassed
Check result
The certificate matches the requested target.
Why it matters
The certificate must list the exact hostname visitors requested in its Subject Alternative Names (SAN). A mismatch produces browser warnings because the certificate may belong to a different service.
What to do
Issue and deploy a certificate whose SAN list includes every public hostname served by this website address.
Recorded data
Certificate domain names:
*.pki.goog, pki.goog
Assessed domain:
pki.goog
Browser-trusted certificateHTTPS and encryptionPassed
Check result
The certificate chains to a trusted root.
Why it matters
Browsers trust a website only when its certificate can be traced to a recognized certificate provider. An untrusted certificate causes warnings and prevents visitors from reliably confirming the website's identity.
What to do
Install a certificate from a provider trusted by common browsers and configure the server to send every required intermediate certificate.
Recorded data
Certificate issuer:
CN=WR2,O=Google Trust Services,C=US
Secure website connection (HTTPS)HTTPS and encryptionPassed
Check result
A TLS handshake succeeded on port 443.
Why it matters
HTTPS encrypts data between visitors and the website and helps prove they reached the intended service. Without it, network observers may read or alter traffic and browsers may show a security warning.
What to do
Provide the entire website over HTTPS using a certificate trusted by common browsers.
Recorded data
Encryption suite:
TLS AES 128 GCM SHA256
IP address:
216.239.32.29
Version:
TLS 1.3
Public DNS recordsDomain and DNSPassed
Check result
The target resolved to 2 public IP address(es).
Why it matters
Public DNS connects the domain to its Internet addresses. Missing or incorrect records can make the service unreachable or send traffic to the wrong system.
What to do
Make sure the domain resolves only to its intended public IP addresses, and remove private, reserved, or outdated records.
Recorded data
IP addresses:
2001:4860:4802:32::1d, 216.239.32.29
Public management service exposurePublic infrastructurePassed
Check result
No public management service was found on the scanned TCP port set.
Why it matters
Remote administration services such as RDP, VNC, Docker, Kubernetes, and management consoles are high-value targets. Public exposure allows anyone on the Internet to attempt passwords or exploit an unpatched service.
What to do
Remove direct Internet access and require a VPN, a hardened access gateway, or trusted source networks; also use MFA where supported.
Database or cache exposed to the InternetPublic infrastructurePassed
Check result
No public datastore service was found on the scanned TCP port set.
Why it matters
Databases and caches often contain sensitive information and are normally used only by internal applications. Direct Internet access makes password attacks and configuration mistakes much more likely to become a data breach.
What to do
Listen only on private interfaces, allow connections only from required application systems, and require strong authentication and encryption.
Recorded data
Complete:
Yes
Fingerprint Complete:
Yes
Fingerprint Identified:
2
Fingerprint Targets:
2
Ports checked:
File-sharing service exposed to the InternetPublic infrastructurePassed
Check result
No public file-sharing service was found on the scanned TCP port set.
Why it matters
Services such as SMB, NFS, and rsync can reveal or modify shared files and have a history of serious vulnerabilities. They rarely need to accept connections directly from the public Internet.
What to do
Limit file-sharing services to private networks or a tightly controlled VPN, and allow only the users and systems that require access.
No public legacy cleartext service was found on the scanned TCP port set.
Why it matters
Older services such as Telnet, FTP, and unencrypted mail or directory protocols can send passwords and data in readable form. Anyone able to observe the network path may capture them.
What to do
Disable the legacy service or replace it with an encrypted alternative such as SSH, SFTP, HTTPS, or the secure version of the mail protocol.
Cross-Origin Resource Sharing (CORS) decides which websites may read responses from this service in a visitor's browser. Rules that trust arbitrary origins, especially with login cookies, can expose private data to another website.
What to do
Allow only explicitly trusted websites, compare the Origin value with an exact approved list, and never allow login credentials with the wildcard origin (*).
Recorded data
Arbitrary origin accepted:
No
Credentials allowed:
No
Allows all origins:
No
Certificate expiry and validityHTTPS and encryptionPassed
Check result
The certificate is valid from 2026-06-29T08:41:51Z to 2026-09-21T08:41:50Z.
Why it matters
A certificate works only between its start and expiry dates. An expired, not-yet-valid, or soon-to-expire certificate can trigger browser warnings and interrupt access to the website or API.
What to do
Use automatic renewal, monitor renewal failures, and alert the responsible team well before expiry.
Recorded data
Days remaining:
62.1
Expires at:
Valid from:
Certificate key and signature strengthHTTPS and encryptionPassed
Check result
The certificate uses SHA256-RSA with a 256-bit public key.
Why it matters
The certificate's public key and signature algorithm protect it from forgery. Keys that are too short or signatures based on obsolete algorithms provide less protection against modern attacks.
What to do
Use RSA with at least 2048 bits or a modern elliptic-curve key, and use SHA-256 or a stronger signature algorithm.
Recorded data
Public-key algorithm:
ECDSA
Public-key size:
256
Signature algorithm:
SHA256-RSA
Supported TLS versionsHTTPS and encryptionPassed
Check result
Accepted versions: TLS 1.2, TLS 1.3.
Why it matters
TLS 1.0 and TLS 1.1 use outdated security designs and are no longer accepted by modern standards. Leaving them enabled allows older, weaker connection methods.
What to do
Disable TLS 1.0 and TLS 1.1, support TLS 1.2 securely, and enable TLS 1.3 where possible.
No independent abuse-list consensus was found across 5 definitive providers.
Why it matters
Security and email providers maintain DNS-based blacklists of IP addresses associated with spam, malware, or compromised systems. Several current, independent listings are a strong reason to investigate, although a shared IP can sometimes affect unrelated customers.
What to do
Verify each listing against the affected IP, investigate mail and host activity, fix the underlying cause, and then follow the provider's removal process.
Recorded data
Blocklists with no match:
5
Confirmed blocklist matches:
No
Blocklists checked conclusively:
5
Blocklists unavailable:
1
DMARC blocking policyEmail protectionPassed
Check result
The effective DMARC policy is reject.
Why it matters
A policy of quarantine or reject tells receiving services to move suspicious mail to spam or refuse it. A monitoring-only policy (p=none) records the problem but does not ask receivers to stop spoofed mail.
What to do
After every legitimate sender passes DMARC, move gradually to quarantine and then reject, covering 100% of messages.
DMARC lets the domain owner tell receiving services what to do when the visible From address is not verified by SPF or DKIM. Without DMARC, attackers have more opportunity to impersonate the domain in phishing email.
What to do
Publish a DMARC record at _dmarc, begin by collecting reports, and confirm that legitimate senders pass before applying a blocking policy.
The core DMARC policy tags passed structural validation.
Why it matters
Receiving services may ignore a DMARC record that contains duplicate fields, invalid values, or is published at the wrong DNS name. An ignored record provides no reliable protection from domain impersonation.
What to do
Publish one valid DMARC record at _dmarc and correct duplicate fields, unsupported values, and invalid report addresses.
An expired domain stops directing users to the organization's services and may eventually become available to someone else. A domain close to expiry leaves little time to recover from payment or account problems.
What to do
Renew well before the expiry date, enable automatic renewal, and protect the payment method and registrar account.
Recorded data
Days remaining:
327.2
Registration expires at:
Domain registration statusDomain and DNSPassed
Check result
RDAP returned 6 status value(s); 0 require attention.
Why it matters
Registrar or registry restrictions such as hold, redemption, or pending deletion can disable the domain. If they are not resolved, the organization may lose control of its website and email identity.
What to do
Resolve registration restrictions promptly, protect the registrar account with MFA, and keep ownership and contact information current.
Recorded data
Registration statuses:
client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Insecure content on an HTTPS pageWebsite protectionPassed
Check result
No issue was found by this check.
Why it matters
An HTTPS page can still load scripts, frames, styles, or forms over unencrypted HTTP. An attacker on the network may alter that content and compromise the otherwise secure page.
What to do
Load every script, frame, stylesheet, and form destination over HTTPS, and remove or replace resources that do not support it.
Without the nosniff setting, a browser may guess a file's type and treat harmless-looking content as executable code. This can turn an incorrect Content-Type into a security issue.
What to do
Send X-Content-Type-Options: nosniff on every response and return an accurate Content-Type.
Complete certificate chainHTTPS and encryptionPassed
Check result
The server presented 3 certificate(s).
Why it matters
The server must provide the intermediate certificates that connect its website certificate to a trusted provider. If any are missing, some browsers, mobile devices, or API clients may reject the connection.
What to do
Configure the server to send the website certificate followed by every required intermediate certificate, but not the root certificate.
Recorded data
Certificates in the chain:
3
Automatic redirect to HTTPSHTTPS and encryptionPassed
Check result
The HTTP root redirects to HTTPS within the target domain.
Why it matters
Visitors may enter an address beginning with HTTP or follow an old link. Redirecting them immediately to HTTPS prevents the rest of the visit from continuing over an unencrypted connection.
What to do
Redirect every HTTP URL directly to its corresponding HTTPS URL without passing through another HTTP address.
Recorded data
Final connection:
https
Website reachable:
Yes
Redirects followed:
1
Public directory listingSoftware vulnerabilitiesPassed
Check result
The root page did not match a common automatic directory-index pattern.
Why it matters
When a web server automatically lists a directory, visitors may discover files that were never linked publicly, including backups, logs, or deployment artifacts.
What to do
Disable automatic directory indexes unless public file browsing is an intentional feature, and remove sensitive files from web-accessible folders.
Recorded data
Directory listing pattern found:
No
Homepage only:
Yes
SPF protection levelEmail protectionPassed
Check result
The terminal SPF policy is -all.
Why it matters
The final SPF rule tells receiving services how confidently they should reject unlisted senders. A permissive result allows more spoofed mail to appear legitimate than a hard fail (-all).
What to do
Confirm that every legitimate sender is included, then end the SPF record with -all.
Sender Policy Framework (SPF) lists the systems allowed to send email for the domain. Without it, receiving services have less evidence to distinguish legitimate mail from spoofed mail.
What to do
Publish one SPF TXT record that includes every legitimate email service and no unauthorized sender.
More than one SPF record, invalid terms, or too many DNS lookups can make SPF return a permanent error. Receiving services may then be unable to verify authorized senders.
What to do
Keep one valid SPF record, remove invalid terms, and remain within the SPF limit of ten DNS-based lookups.
No matching credential exposure records were found in the currently indexed intelligence data. This does not prove that no exposure exists.
Why it matters
Infostealer intelligence may contain credentials associated with the domain, but it does not prove that an account is current, valid, or still exposed.
What to do
Review the masked evidence and observation time, validate affected accounts and devices, then reset active credentials and sessions, enforce MFA, and remove malware where confirmed.
Recorded data
Distinct affected devices observed:
0
Estimated infostealer-infected devices:
0
Evidence samples shown:
0
Evidence sample limit:
10
Email routing records (MX)Domain and DNSPassed
Check result
Found 1 MX record(s); 0 target(s) were invalid.
Why it matters
MX records direct incoming email to the correct mail servers. Broken records can stop delivery, while a Null MX clearly tells senders that the domain does not receive email.
What to do
Correct unreachable or outdated MX hosts, or publish a Null MX if the domain is not intended to receive email.
Recorded data
Does not receive email:
No
Unnecessary public servicesPublic infrastructurePassed
Check result
No public unexpected service was found on the scanned TCP port set.
Why it matters
Every open service can be discovered and attacked and must be configured, monitored, and patched. Services without a clear public purpose add risk without providing business value.
What to do
Confirm the owner and purpose of every open port, then stop or firewall any service that is not intentionally public.
Exact web server or framework versions help attackers quickly look for known weaknesses that may apply. Hiding a version is not a substitute for patching, but unnecessary disclosure gives away useful targeting information.
What to do
Remove unnecessary version details from Server, X-Powered-By, error pages, and application metadata, and keep the software patched.
DMARC monitoring reportsEmail protectionPassed
Check result
Aggregate reporting is configured.
Why it matters
DMARC aggregate reports show which systems send email using the domain and which messages fail verification. They help find both impersonation attempts and legitimate services that need correction.
What to do
Add an aggregate report address (rua) that is protected and monitored, or use a trusted DMARC reporting service.
A domain should clearly state whether it receives email. Without valid MX records or a Null MX, senders may try an unintended server and delivery behavior becomes unpredictable.
What to do
Publish valid MX records for the intended mail servers, or a Null MX if the domain never accepts email.
Recorded data
Does not receive email:
No
Allowed certificate issuers (CAA)Domain and DNSPassed
Check result
Found 1 applicable CAA record(s).
Why it matters
Certificate Authority Authorization (CAA) records state which certificate providers may issue certificates for the domain. This reduces the chance of an unintended provider issuing one.
What to do
Publish CAA records that allow only the certificate providers your organization actually uses.
DNS response protection (DNSSEC)Domain and DNSPassed
Check result
A DNSSEC DS delegation was found.
Why it matters
DNSSEC adds digital signatures so resolvers can detect forged DNS answers. This quick check confirms the parent domain has a DS record, but it does not validate the complete signature chain.
What to do
Sign the DNS zone, publish the matching DS record through the registrar, and monitor the signature chain after key changes.
Authoritative name servers tell visitors where the domain is hosted. Depending on only one server creates a single point of failure for the website and email.
What to do
Use at least two authoritative name servers, preferably on independent and resilient infrastructure.
Password form transport securityWebsite protectionNot applicable
Check result
This check does not apply to the target.
Why it matters
If either a password page or the address receiving its form uses HTTP, someone observing the network may read or change the submitted password.
What to do
Serve every page containing a password field over HTTPS and submit each password form directly to an HTTPS address.
Recorded data
Password forms:
0
Session cookies protected from scripts (HttpOnly)Website protectionNot applicable
Check result
This check does not apply to the target.
Why it matters
HttpOnly prevents browser scripts from directly reading a cookie. It does not fix script injection, but it makes theft of session and authentication cookies more difficult.
What to do
Set HttpOnly on session and authentication cookies unless the application has a documented need to read them in browser code.
Cookies sent only over HTTPS (Secure)Website protectionNot applicable
Check result
This check does not apply to the target.
Why it matters
The Secure attribute prevents a browser from sending a cookie over unencrypted HTTP. Without it, session or authentication data may be exposed to someone observing the network.
What to do
Set Secure on every session, authentication, and other sensitive cookie served by the HTTPS application.
SameSite limits when a browser includes cookies in requests started by another website. This helps prevent another site from silently making an authenticated request on a user's behalf.
What to do
Use SameSite=Lax or Strict by default. Use SameSite=None only for a required cross-site flow and always combine it with Secure.
HSTS protection periodHTTPS and encryptionNot applicable
Check result
This check does not apply to the target.
Why it matters
The max-age value controls how long browsers remember to use HTTPS. A very short period provides limited protection, while includeSubDomains also covers every subdomain and can break one that does not support HTTPS.
What to do
Use a long max-age, and add includeSubDomains only after confirming that every active subdomain works correctly over HTTPS.
Observed infrastructure
Addresses, servers and services that are visible from the Internet.
2
Resolved addresses
2
Addresses scanned
Ssffe
Server
—
Operating system
Public infrastructure and exposed software
Each public IP is grouped with its open services, identified products and any CVEs that may apply to the observed version.
58 tcp ports tested · Complete
IP addressHosting or network providerNetwork locationOpen network services
Potentially exposed domain email addressesChecks infostealer data only for email addresses whose domain exactly matches this target. A record is not counted merely because someone visited or signed in to this website.0 Matching email exposure records
0Matching email exposure records
0Related infected devices (estimated)
No exposure record was found for an email address whose domain exactly matches this target. This does not guarantee that an exposure has never occurred.
Discovered subdomains (1,500+)Subdomains discovered by CyStack, with sensitive-looking names shown first. Availability is verified during this assessment; individual subdomains have not been separately security-tested.Partial
Results were bounded and may be truncated.
admin.1.pki.googSensitive-lookingAdmin system
admin.2.pki.googSensitive-lookingAdmin system
admin.3.pki.googSensitive-lookingAdmin system
admin.account.pki.goog
Public web contextThe website title, description, industry and popularity.
Page title
Google Trust Services | Home
Website category
Computers, Electronics and Technology / Computer Security
Description
Google Trust Services
Global rank
#549,606
Rank in United States
#461,397
Rank in industry
#1,033
This is a quick, point-in-time check from outside the organization. It can surface visible risks, but it does not replace penetration testing or an authenticated assessment.
Which public IPs, services, and ports does pki.goog expose?
The assessment observed 2 public IPs and 2 open ports for pki.goog; the infrastructure appears to be operated by Google LLC. An open port is not automatically a vulnerability, but every public service should be updated and appropriately restricted.
The assessment observed 1,500+ public subdomains of pki.goog. This inventory can reveal additional entry points such as APIs, administration systems, or test environments, but it does not imply that every subdomain is risky.
GGoogle Tag ManagerVersion not visibleTag ManagersVersion not visible
ConfidenceMedium
Google Tag Manager is a tag management system (TMS) that allows you to quickly and easily update measurement codes and related code fragments collectively known as tags on your website or mobile app.
Client Delete Prohibited, Client Transfer Prohibited, Client Update Prohibited, Server Delete Prohibited, Server Transfer Prohibited, Server Update Prohibited
Sensitive-lookingAdmin systemLogin system
admin.accounts.pki.googSensitive-lookingAdmin systemLogin system
admin.ad1.pki.googSensitive-lookingAdmin system
admin.adminer.pki.googSensitive-lookingAdmin systemData system
admin.ads.pki.googSensitive-lookingAdmin system
admin.adserver.pki.googSensitive-lookingAdmin system
Google AnalyticsG
Google Tag ManagerH
Hammer.js+2
HTTP/3MiscellaneousVersion not visible
reCAPTCHASecurityVersion not visible
