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.
BDNS Records2 A records, 129 ms lookupREVIEW
| A | 2.16.6.30, 2.16.6.18 |
| AAAA | 2a02:26f0:1180:7b::215:178b, 2a02:26f0:1180:7b::215:17ab |
| CNAME | e111296.dsca.akamaiedge.net |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
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.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
BCrawlabilityrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
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.
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
User-agent: *
Allow: /
Allow: /de/careers/?*
Allow: /?location=home
Allow: /Tracking?cntry_code=us
Allow: /apps/fedextrack/?action=track
Allow: /en-us/home.html?location=home
Allow: /locate/index.html?locale=en_US
Allow: /en-us/tracking.html?action=track
Allow: /global/choose-location.html?location=home
Allow: /ratefinder/home?cc=US&language=en&locId=express
Allow: /apps/fedextrack/?action=track&cntry_code=us&freight=yes
Allow: /fedextrack/?cntry_code=us&tab=1&tracknums=&clienttype=wtrk
Disallow: /*?*
Disallow: /libs/
Disallow: /en-us/quick-help/*
Disallow: /en-us/GDCMTestSites/*
Disallow: /us/developer/WebHelp/*
Disallow: /content/dam/fedex-com/hdn/
Sitemap: https://www.fedex.com/en-us/sitemap.xml
Sitemap: https://www.fedex.com/global/sitemap_index.xml
Disallow: /content/fedex-com/global/en_us/*
Disallow: /content/fedex-com/sites/us/*
Disallow: /content/fedex-com/sites/*
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Preferred variant: www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations151 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- 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+Redirect ChainNo redirects — direct accessPASS
https://www.fedex.com
392 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.fedex.com | 200 | 392 ms | HTTP/1.1 | AkamaiNetStorage |
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Domain Intelligencefedex.com — via CSC Corporate Domains, Inc., 35 years, 7 months old, hosted on FITC-AS - FedEx Internet Technologies Corporation, USPASS
140 days
November 29, 2026
151 days
Issued by Sectigo Limited
35 years, 7 months
Registered February 26, 1991
Not enabled
Protects against DNS spoofing
FITC-AS - FedEx Internet Technologies Corporation, US
ASN AS7726
170.170.193.102
CSC Corporate Domains, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
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