Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FRedirect ChainAction3 redirect(s), 1623 ms totalFIX
https://paypal.me
16 ms · HTTP/1.1
https://www.paypal.me/
242 ms · HTTP/1.1
https://www.paypal.com/paypalme/
283 ms · HTTP/1.1
https://www.paypal.com/br/webapps/mpp/ho...
1082 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://paypal.me | 301 | 16 ms | HTTP/1.1 | Varnish |
| 2 | https://www.paypal.me/ | 301 | 242 ms | HTTP/1.1 | cloudflare |
| 3 | https://www.paypal.com/paypalme/ | 302 | 283 ms | HTTP/1.1 | cloudflare |
| 4 | https://www.paypal.com/br/webapps/mpp/ho... | 200 | 1082 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
DCrawlabilityActionrobots.txt present, no sitemapFIX
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.
Learn more ▾ ▴
Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.
Source: Google Search Central
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
# PP.me robots.txt --
User-agent: Twitterbot
Disallow:
User-agent: facebookexternalhit
Disallow:
User-agent: *
Disallow: /
Allow: /pages/faqs
Allow: /pages/terms
Allow: /$
No sitemap found
Adding a sitemap helps search engines discover your pages.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations178 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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 Records3 A records, 13 ms lookupPASS
| A | 151.101.65.21, 151.101.129.21, 162.159.141.96 |
| AAAA | — |
| CNAME | — |
| NS | pdns100.ultradns.com, pdns100.ultradns.net, ns1-pchnet.paypal.com, ns2-pchnet.paypal.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 mx1.paypalcorp.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | SPF v=spf1 -all 4tq9gwcyb51hm86yvjr684dhkqh9b1xy |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
ADomain Intelligencepaypal.me — via MarkMonitor Inc., 18 years, 1 months old, hosted on FastlyPASS
EXPIRED
June 13, 2026
178 days
Issued by DigiCert Inc
18 years, 1 months
Registered June 13, 2008
Status unknown
Protects against DNS spoofing
Fastly
ASN AS54113
151.101.65.21
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Domain has EXPIRED — renew immediately to avoid total site outage
Consider enabling auto-renewal to prevent accidental expiration.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.
Source: ICANN / domain-security best practice