Skip to content
https://pg.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 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
Redirect Chain
2 redirect(s), 962 ms total
REVIEW
2 redirect(s), 962 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Redirect overhead: 962 ms total
Got: 962 ms
Info::
Cross-domain redirect detected

https://pg.com

393 ms · HTTP/1.1

301

https://www.pg.com/

119 ms · HTTP/1.1

301

https://us.pg.com/

450 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pg.com301393 msHTTP/1.1Microsoft-Azure-Application-Gateway/v2
2https://www.pg.com/301119 msHTTP/1.1
3https://us.pg.com/200450 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 71 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 71 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /
Sitemap: https://www.pg.com//patents/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
345 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
A+
DNS Records
1 A records, 95 ms lookup
PASS
1 A records, 95 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 20.88.104.223
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns2-05.azure-dns.net, ns1-05.azure-dns.com, ns4-05.azure-dns.info, ns3-05.azure-dns.org
Info::
2 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: 95 ms
Got: 95 ms
A20.88.104.223
AAAA
CNAME
NSns2-05.azure-dns.net, ns1-05.azure-dns.com, ns4-05.azure-dns.info, ns3-05.azure-dns.org
MX
10 mxb-0019c602.gslb.pphosted.com
10 mxa-0019c602.gslb.pphosted.com
TXT
sz64ndladhjj736daq3zy5v4yoj4p2tr._domainkey
segment-site-verification=RuYT93COeDtS3er1Dz3s6DvPxMFIuwQk
vmware-cloud-verification-2edb2741-788c-4f38-a905-d9a7f8114381
liveramp-site-verification=c-MMCEkHC24GLv8iSUUbtqO9W4IlxTSf9oJAWv_fPoE
status-page-domain-verification=zvbs0blx9p9f
google-site-verification=61-6XYAP7lg2GCaeD1oYpkJLUhJ7JZPrwIMOALhHHuI
tiktok-developers-site-verification=VB70lbsaxh4onaUe8OsmCvrjlJrP9wrb
ciscocidomainverification=cabefe53be72f9262c9b8bb36fd640b1686303c38d28c95c9aea81...
TAILSCALE-ofWFd9OcFJWcIOfuLI2L
atlassian-domain-verification=D9CTDfLYlkPRjT5SB1gCYlrgLcAzO0ZAe8zBX6rrtUlyvqfh8F...
atlassian-domain-verification=FpRqwp3wdbQ12wVqkqTzs7kJPDue+u0VIc2k5rGP6K6VtCLr8p...
adobe-sign-verification=6202d0d99d6c9925c7193c3d8b89c48d
SPF v=spf1 include:spf.protection.outlook.com ip4:148.163.135.172 ip4:148.163.139.17...
successfactors-site-verification=MGU2NTU0YmY4MzhlMDk0Yjk4MWFiY2ZjYmJhNjczZDY5ZWE...
yandex-verification: 449bcb2b45741a4a
duhxjhdciomliox6oaohayho6yk2jn3c._domainkey
+R7950bwe1bc/LH4ilGOC4l14eTYzYoKFwzRRJeTuDb+yzmijiAQGiNdCb0eiPB5MnDSLk+L0cKP2RtU...
flexera-domain-verification-bbqptgkaxclwsssp
c6q4by6wew7mvyfjt3gaqs6r7uegcj5q._domainkey
autodesk-domain-verification=1UMtoeI4vNgaIUFop2Lq
shopify-verification-code=vrmNtGXpynqaqxQj9GYed0zS5YgUit
airtable-verification=c7d1858c9aaea0f12b807ed8a72a67a8
Yfr5BaCoZDtixZ/ynyfWaYdCk0jfGQE1ReIiCgywBH+9Pw+j1Tk1NDS9lv2umIS4+KPtfgArrBu8/gOd...
o1lbi9rj1f0ohnkh2q2c1su6t
asv=a46b01e73fb64b46cb9beb54992c8a29
docker-verification=787050b1-54ac-4a98-92f9-2046698ce0ac
extensis-domain-verification=85433ced-47a0-4f92-9764-3839c1f5b837
CAALookup not available with standard resolver
Resolved in 95 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+
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.pg.com/
200https://pg.com/

Preferred variant: non-www

HTTP → HTTPS

301http://pg.com/ https://pg.com/

Consistent

A+
Domain Intelligence
pg.com — via CSC Corporate Domains, Inc., 34 years, 7 months old, hosted on Microsoft Azure
PASS
pg.com — via CSC Corporate Domains, Inc., 34 years, 7 months old, hosted on Microsoft Azure
Info::
Domain registered until Feb 25, 2027 (10 months 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: CSC Corporate Domains, 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.
Info::
Hosting: Microsoft Azure
Got: AS8075
Domain expiry

224 days

February 25, 2027

SSL certificate

345 days

Issued by Sectigo Limited

Domain age

34 years, 7 months

Registered February 24, 1992

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

20.88.104.223

Registrar

CSC Corporate Domains, Inc.

Unlocked 4 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 CSC Corporate Domains, Inc.
Created February 24, 1992 (34 years, 7 months ago)
Expires February 25, 2027 (10 months)
Last Updated February 21, 2026
Name Servers ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info
DNSSEC Not enabled
Hosting
IP Address 20.88.104.223
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 29 ms TCP Connect 98 ms TLS Handshake 198 ms Server Processing 97 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback