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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
1
PASS
8
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
8 PASS 1 REVIEW
B
TLS Certificate Expiry & Recommendations
165 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

165
days left
0d 30d 60d 90d+

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
DNS Records
4 A records, 43 ms lookup
PASS
4 A records, 43 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 143.204.55.127, 143.204.55.68, 143.204.55.25, 143.204.55.102
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:20a5:4000:e:613c:fac0:93a1, 2600:9000:20a5:3a00:e:613c:fac0:93a1, 2600:9000:20a5:f000:e:613c:fac0:93a1, 2600:9000:20a5:6c00:e:613c:fac0:93a1, 2600:9000:20a5:2c00:e:613c:fac0:93a1, 2600:9000:20a5:1c00:e:613c:fac0:93a1, 2600:9000:20a5:7400:e:613c:fac0:93a1, 2600:9000:20a5:4e00:e:613c:fac0:93a1
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: d6jdux3y9l697.cloudfront.net
Info::
4 nameserver(s) configured
Got: ns-604.awsdns-11.net, ns-1333.awsdns-38.org, ns-2022.awsdns-60.co.uk, ns-162.awsdns-20.com
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: 43 ms
Got: 43 ms
A143.204.55.127, 143.204.55.68, 143.204.55.25, 143.204.55.102
AAAA2600:9000:20a5:4000:e:613c:fac0:93a1, 2600:9000:20a5:3a00:e:613c:fac0:93a1, 2600:9000:20a5:f000:e:613c:fac0:93a1, 2600:9000:20a5:6c00:e:613c:fac0:93a1, 2600:9000:20a5:2c00:e:613c:fac0:93a1, 2600:9000:20a5:1c00:e:613c:fac0:93a1, 2600:9000:20a5:7400:e:613c:fac0:93a1, 2600:9000:20a5:4e00:e:613c:fac0:93a1
CNAMEd6jdux3y9l697.cloudfront.net
NSns-604.awsdns-11.net, ns-1333.awsdns-38.org, ns-2022.awsdns-60.co.uk, ns-162.awsdns-20.com
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 43 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

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.

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
1 redirect(s), 250 ms total
PASS
1 redirect(s), 250 ms total
Info::
Single redirect
Got: https://www.datadog.com → https://www.datadoghq.com/ (301)
Info::
Cross-domain redirect detected

https://www.datadog.com

103 ms · HTTP/1.1

301

https://www.datadoghq.com/

147 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.datadog.com301103 msHTTP/1.1AmazonS3
2https://www.datadoghq.com/200147 msHTTP/1.1AmazonS3

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (31 ms)
PASS
IPv6 reachable (31 ms)
Info::
IPv6 is configured and reachable at 2600:9000:20a5:4000:e:613c:fac0:93a1, 2600:9000:20a5:3a00:e:613c:fac0:93a1, 2600:9000:20a5:f000:e:613c:fac0:93a1, 2600:9000:20a5:6c00:e:613c:fac0:93a1, 2600:9000:20a5:2c00:e:613c:fac0:93a1, 2600:9000:20a5:1c00:e:613c:fac0:93a1, 2600:9000:20a5:7400:e:613c:fac0:93a1, 2600:9000:20a5:4e00:e:613c:fac0:93a1
Got: 31 ms connect
IPv6 Ready
AAAA Records 2600:9000:20a5:4000:e:613c:fac0:93a1, 2600:9000:20a5:3a00:e:613c:fac0:93a1, 2600:9000:20a5:f000:e:613c:fac0:93a1, 2600:9000:20a5:6c00:e:613c:fac0:93a1, 2600:9000:20a5:2c00:e:613c:fac0:93a1, 2600:9000:20a5:1c00:e:613c:fac0:93a1, 2600:9000:20a5:7400:e:613c:fac0:93a1, 2600:9000:20a5:4e00:e:613c:fac0:93a1 Connection Reachable (31 ms)
A+
Crawlability
robots.txt present, sitemap with 14 URLs
PASS
robots.txt present, sitemap with 14 URLs
Info::
robots.txt is present
Got: 525 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 14 entries
Info::
Sitemap index with 14 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 525 B Sitemaps referenced 9 User-agents * Blocking No — crawling allowed
User-agent: * 
Disallow: /pdf/
Disallow: /meta/
Disallow: /style/

#Sitemaps
Sitemap: https://www.datadoghq.com/sitemap.xml
Sitemap: https://www.datadoghq.com/en/sitemap.xml
Sitemap: https://www.datadoghq.com/es/sitemap.xml
Sitemap: https://www.datadoghq.com/ja/sitemap.xml
Sitemap: https://www.datadoghq.com/fr/sitemap.xml
Sitemap: https://www.datadoghq.com/de/sitemap.xml
Sitemap: https://www.datadoghq.com/it/sitemap.xml
Sitemap: https://www.datadoghq.com/ko/sitemap.xml
Sitemap: https://www.datadoghq.com/pt/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 14 entries Valid XML Yes
Child Sitemaps:
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.datadog.com/
301https://datadog.com/

Preferred variant: www

HTTP → HTTPS

301http://www.datadog.com/ → https://www.datadog.com/

Consistent

A+
Domain Intelligence
datadog.com — via NameCheap, Inc., 29 years, 8 months old, hosted on AWS
PASS
datadog.com — via NameCheap, Inc., 29 years, 8 months old, hosted on AWS
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: NameCheap, Inc.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

203 days

January 5, 2027

SSL certificate

165 days

Issued by DigiCert Inc

Domain age

29 years, 8 months

Registered January 6, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

143.204.55.127

Registrar

NameCheap, Inc.

Lock status unknown 4 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 NameCheap, Inc.
Created January 6, 1997 (29 years, 8 months ago)
Expires January 5, 2027 (9 months)
Last Updated December 6, 2025
Name Servers ns-1531.awsdns-63.org, ns-1629.awsdns-11.co.uk, ns-382.awsdns-47.com, ns-707.awsdns-24.net
DNSSEC Not enabled
Hosting
IP Address 143.204.55.127
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)

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 165 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
57 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
33 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
37 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
165 ms
Total Time Total request time from DNS lookup through full response.
165 ms

Connection waterfall

DNS Lookup 57 ms TCP Connect 33 ms TLS Handshake 37 ms Server Processing 38 ms Content Transfer 0 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: ZRH52-P1)
Got: x-amz-cf-id: zdvXsRWM1lbsi-AvFueFNgX6Sfq9tk3iLNqSQj8YePoT-IXKgdXqMQ==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: zdvXsRWM1lbsi-AvFueFNgX6Sfq9tk3iLNqSQj8YePoT-IXKgdXqMQ==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback