Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNS Records1 A records, 34 ms lookupREVIEW
| A | 23.194.22.230 |
| AAAA | 2a02:26f0:2380:4aa::c3a, 2a02:26f0:2380:492::c3a |
| CNAME | paloaltonetworks.com.edgekey.net |
| NS | — |
| MX | — |
| TXT | — |
| 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
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 3805 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
User-agent: *
Disallow: /content/dam/
Disallow: /content/dam/pan/en_US/assets/pdf/legal/archive/
Disallow: /content/pan/en_US/content/dam
Disallow: /content/pan/en_US/partners/nextwave-partner-portal/
Disallow: /content/pan/en_US/field/
Disallow: /content/pan/en_US/ignitePromoDemo
Disallow: /content/pan/en_US/legal-notices/privacy/privacy-notice
Disallow: /content/pan/en_US/
Disallow: /content/pan/ja_JP/
Disallow: /content/pan/de_DE/
Disallow: /content/pan/fr_FR/
Disallow: /content/pan/es_ES/
Disallow: /content/pan/pt_BR/
Disallow: /content/pan/en_AU/
Disallow: /content/pan/zh_TW/
Disallow: /content/pan/ko_KR/
Disallow: /content/pan/zh_CN/
Disallow: /content/pan/es_LA/
Disallow: /content/pan/en_US/allsitemap.html
Disallow: /static/
Disallow: /static_260619/
Disallow: /static_perf/
Disallow: /qa/
Disallow: /allsitemap
Disallow: /allsitemap.html
Disallow: /content/pan/en_US/sitemaps/
Disallow: /sitemaps/
Disallow: /content/pan/en_GB/
Disallow: /content/pan/en_CA/
Disallow: /content/pan/en_SG/
Disallow: /content/pan/en_IN/
Disallow: /content/pan/it_IT/
Disallow: /content/pan/es_MX/
Disallow: /content/pan/en_US/topNav/
Disallow: /content/pan/en_US/newTopNav/
Disallow: /content/pan/en_US/expandedTopNav/
Disallow: /apps/
Allow: /apps/pan/public/singlePageReactModel?pageId=
Allow: /apps/pan/public/unit42/bloglist.loadblogresults.json?searchLanguage=en_US
Disallow: /content/pan-dev
Disallow: /content/pan/en_US/healthCheck.html
Disallow: /content/pan/en_US/events/xdr-event
Disallow: /content/pan/en_US/events/xdr-event.html
Disallow: /content/pan/en_US/events/xdr-post-event
Disallow: /content/pan/en_US/events/xdr-post-event.html
Disallow: /content/pan/en_US/atlassian-domain-verification.html
Allow: /sitemap.xml
Disallow: /content/pan/en_US/documentation/
Disallow: /documentation/
Disallow: /company/in-the-news/2019/
Disallow: /company/in-the-news/2018/
Disallow: /company/in-the-news/2017/
Disallow: /company/in-the-news/2016/
Disallow: /company/in-the-news/2015/
Disallow: /company/in-the-news/2014/
Disallow: /company/in-the-news/2013/
Disallow: /company/in-the-news/2012/
Disallow: /company/in-the-news/2011/
Disallow: /company/in-the-news/2010/
Disallow: /company/in-the-news/2009/
Disallow: /company/in-the-news/2008/
Disallow: /company/in-the-news/2007/
Disallow: /company/press/2019/
Disallow: /company/press/2018/
Disallow: /company/press/2017/
Disallow: /company/press/2016/
Disallow: /company/press/2015/
Disallow: /company/press/2014/
Disallow: /company/press/2013/
Disallow: /company/press/2012/
Disallow: /company/press/2011/
Disallow: /company/press/2010/
Disallow: /company/press/2009/
Disallow: /company/press/2008/
Disallow: /company/press/2007/
Disallow: /securityevent/en_US_LV2.html
Disallow: /content/pan/en_US/google992ef19868c7ad5e.html
Disallow: /google992ef19868c7ad5e.html
Disallow: /content/pan/en_US/.well_known/
Disallow: /.well_known/
Disallow: /events/future-of-security-revealed
Disallow: /events/future-of-security-revealed-amer
Disallow: /newbrand
Allow: /content/dam/*.svg$
Allow: /content/dam/*.gif$
Allow: /content/dam/*.png$
Allow: /content/dam/*.jpg$
Allow: /content/dam/*.jpeg$
Allow: /content/dam/*.svg$
Allow: /content/dam/*.gif?imwidth
Allow: /content/dam/*.png?imwidth
Allow: /content/dam/*.jpg?imwidth
Allow: /content/dam/*.jpeg?imwidth
Allow: /content/dam/*.js$
Allow: /content/dam/*.css$
Disallow: /blog/wp-admin/
Allow: /blog/wp-admin/admin-ajax.php
Disallow: /devsectalks/wp-admin/
Allow: /devsectalks/wp-admin/admin-ajax.php
Disallow: /perspectives/wp-admin/
Allow: /perspectives/wp-admin/admin-ajax.php
Sitemap: https://www.paloaltonetworks.com/sitemap.xml
Sitemap: https://www.paloaltonetworks.com/sitemap_home.xml
Sitemap: https://www.paloaltonetworks.com/blog/sitemap_index.xml
Sitemap: https://www.paloaltonetworks.com/devsectalks/sitemap_index.xml
Sitemap: https://www.paloaltonetworks.com/perspectives/sitemap_index.xml
User-agent: Twitterbot
Allow: /*.gif$
Allow: /*.png$
Allow: /*.jpg$
BTLS Certificate Expiry & Recommendations281 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
BCDN & DeliveryAkamaiREVIEW
A+Redirect ChainNo redirects — direct accessPASS
https://www.paloaltonetworks.com
166 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.paloaltonetworks.com | 200 | 166 ms | HTTP/1.1 | Apache |
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligencepaloaltonetworks.com — via MarkMonitor Inc., 21 years, 5 months old, hosted on Google CloudPASS
588 days
February 21, 2028
281 days
Issued by DigiCert Inc
21 years, 5 months
Registered February 21, 2005
Enabled
Protects against DNS spoofing
Google Cloud
ASN AS396982
34.107.151.202
MarkMonitor Inc.