Is googleapis.com safe to use as a vendor?

googleapis.com scored 78/100 on LynxRadar's security posture assessment. The domain partially meets security requirements with some gaps to address. 8 checks passed, 4 warnings, 2 critical issues across 14 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

Does googleapis.com have security headers configured?

googleapis.com has 1 of 5 recommended security headers. Present: Referrer-Policy. Missing: CSP, X-Content-Type-Options, X-Frame-Options, Permissions-Policy.

googleapis.com Security Report — Grade C+ (78/100)

Q: What TLS version does googleapis.com use?

googleapis.com uses TLSv1.3 with TLS_AES_256_GCM_SHA384. TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Q: Does googleapis.com have DMARC configured?

Yes. googleapis.com's DMARC policy is set to 'reject'. SPF record: yes. Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 0/10 (within limit). Issues: No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).

Q: Does googleapis.com use HSTS?

No. Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks. If this domain is in the browser HSTS preload list, browsers may still enforce HTTPS — but the header should be present for full coverage.

Q: Is googleapis.com's SSL certificate valid?

Yes. Strengths: Certificate valid, 57 days remaining; Issued by Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.

Q: Does googleapis.com have DNSSEC enabled?

No. Strengths: 4 nameservers configured (ns4.google.com, ns3.google.com, ns1.google.com, ns2.google.com); SOA record present and MNAME consistent with NS set; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s), 1 AAAA record(s). Issues: All nameservers are from a single provider (google.com) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

C+ 78/100

googleapis.com

June 20, 2026 ·

1+ Warnings 8 Passed

Better than 59% of 2692 companies scanned.

059th pct100

A+

A-

B+

B-

C+

C-

D+

D-

HSTS Header

Security Headers

MTA-STS & TLS Reporting

DNS CAA Records

DNS Configuration

security.txt (RFC 9116)

C+

googleapis.com

78/100

Enable HSTS (HTTP Strict Transport Security)

HSTS Header

< 1 hour

The HSTS header is missing on googleapis.com. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.

PCI-DSS 4.0Req 6.4.1

Required application security controls

NIST 800-53SC-8

Transmission confidentiality and integrity

How to fix this

1Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

2Verify all subdomains support HTTPS before adding includeSubDomains

3Test with: curl -sI https://googleapis.com | grep -i strict

4Submit to hstspreload.org after confirming the header is correct

At a glance

Full data from this scan

TLS Version

TLSv1.3

TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

DMARC Policy

p=reject

Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 0/10 (within limit). Issues: No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).

SPF Record

Present

v=spf1 -all

Security Headers

1/5 present

Missing: CSP, X-Content-Type-Options, X-Frame-Options, Permissions-Policy

HSTS

Not enabled

Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks. If this domain is in the browser HSTS preload list, browsers may still enforce HTTPS — but the header should be present for full coverage.

SSL Certificate

Valid

Strengths: Certificate valid, 57 days remaining; Issued by Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.

DNSSEC

Not enabled

Strengths: 4 nameservers configured (ns4.google.com, ns3.google.com, ns1.google.com, ns2.google.com); SOA record present and MNAME consistent with NS set; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s), 1 AAAA record(s). Issues: All nameservers are from a single provider (google.com) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

Similar companies