Skip to content
https://www.palantir.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
7 PASS 2 REVIEW
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
TLS Certificate Expiry & Recommendations
351 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

351
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
  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
4 A records, 38 ms lookup
PASS
4 A records, 38 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.193.170, 151.101.129.170, 151.101.1.170, 151.101.65.170
Info::
No IPv6 (AAAA) records
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 38 ms
Got: 38 ms
A151.101.193.170, 151.101.129.170, 151.101.1.170, 151.101.65.170
AAAA
CNAME
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 38 ms

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

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)

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.palantir.com

https://www.palantir.com

13 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.palantir.com20013 msHTTP/1.1AmazonS3
A+
Crawlability
robots.txt present, sitemap with 642 URLs
PASS
robots.txt present, sitemap with 642 URLs
Info::
robots.txt is present
Got: 188 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 642 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 188 B Sitemaps referenced 2 User-agents GPTBot Blocking No — crawling allowed
# GPTBot
User-agent: GPTBot
Disallow: /

# Host
Host: https://www.palantir.com

# Sitemaps
Sitemap: https://www.palantir.com/sitemap.xml
Sitemap: https://www.palantir.com/docs/sitemap.xml

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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.palantir.com/
302https://palantir.com/

Preferred variant: www

HTTP → HTTPS

301http://www.palantir.com/ https://www.palantir.com/

Consistent

A+
Domain Intelligence
palantir.com — via MarkMonitor Inc., 33 years, 8 months old, hosted on Fastly
PASS
palantir.com — via MarkMonitor Inc., 33 years, 8 months old, hosted on Fastly
Info::
Domain registered until Jan 5, 2027 (9 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: MarkMonitor Inc.
Info::
Hosting: Fastly
Got: AS54113
Domain expiry

205 days

January 5, 2027

SSL certificate

351 days

Issued by GlobalSign nv-sa

Domain age

33 years, 8 months

Registered January 6, 1993

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.193.170

Registrar

MarkMonitor Inc.

Lock status unknown 8 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
Registrar MarkMonitor Inc.
Created January 6, 1993 (33 years, 8 months ago)
Expires January 5, 2027 (9 months)
Last Updated December 4, 2025
Name Servers ns-1128.awsdns-13.org, ns-1922.awsdns-48.co.uk, ns-7.awsdns-00.com, ns-832.awsdns-40.net, ns1-08.azure-dns.com, ns2-08.azure-dns.net, ns3-08.azure-dns.org, ns4-08.azure-dns.info
DNSSEC Not enabled
Hosting
IP Address 151.101.193.170
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
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

A+
HTTP Probe Timing
Total 47 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
40 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
46 ms
Total Time Total request time from DNS lookup through full response.
48 ms

Connection waterfall

DNS Lookup 40 ms TCP Connect 0 ms TLS Handshake 5 ms Server Processing 1 ms Content Transfer 1 ms
A+
CDN & Delivery
Fastly (HIT)
PASS
Fastly (HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-toj-leto2350075-TOJ
Info::
CDN cache status: HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT Evidence x-served-by: cache-toj-leto2350075-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback