Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations71 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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 Records1 A records, 190 ms lookupPASS
| A | 56.0.134.100 |
| AAAA | — |
| CNAME | — |
| NS | dns141.usps.com, dns082.usps.com |
| MX | 10 mxb-0038fd02.gslb.gpphosted.com 10 mxa-0038fd02.gslb.gpphosted.com |
| TXT | t5cmxmtc9bsyn3lnh9cp61w7zl6p9dmh apple-domain-verification=1mTpTvcYUbpLD2DCGn6S7e8E7GNEuCbLmsnOVoINlXk MS=ms75843013 google-site-verification=g8v2m4CGzjzeR7BlXEWdkPw_Vee3KLd5Msu1oxq9X4Y m8gzt1kxn0b8hm22m2154p7dgkwrqllc U0S4P86940 xh9xzqypj83py3z3049hr39d5m75sffn 5gnbvs23tq9vmq20zmtgsydzs39qpksb MS=891EBC03C14DB5081F9801A66F922A606978EBD3 SPF v=spf1 ip4:56.0.0.0/16 -all wbbcfpqr2lfkgls6hh8gtxrn3y16p7yx |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 570 ms totalPASS
https://usps.com
511 ms · HTTP/1.1
https://www.usps.com/
59 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://usps.com | 301 | 511 ms | HTTP/1.1 | |
| 2 | https://www.usps.com/ | 200 | 59 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 90 URLsPASS
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
User-agent: *
Disallow: /ContentTemplates/
Disallow: /root/
Disallow: /business/global/
Disallow: /manage/global/
Disallow: /send/global/
Disallow: /ship/global/
Disallow: /shop/global/
Disallow: /go/tools/po-locator/po-locator.html
Disallow: /go/tools/track-confirm/quick-track.html
Disallow: /go/tools/zip-code-lookup/quick-zip.html
Disallow: /shippingassistant/
Disallow: /business/shipping-assistant.htm
Disallow: /leadingtogether/
ADomain Intelligenceusps.com — via Network Solutions, LLC, 29 years, 2 months old, hosted on USPS-001 - United States Postal Service, USPASS
23 days
July 9, 2026
71 days
Issued by Sectigo Limited
29 years, 2 months
Registered July 10, 1997
Not enabled
Protects against DNS spoofing
USPS-001 - United States Postal Service, US
ASN AS5774
56.0.134.100
Network Solutions, LLC
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Consider enabling auto-renewal to prevent accidental expiration.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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