Skip to content
https://bugsnag.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.bugsnag.com/
200https://bugsnag.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://bugsnag.com/ https://bugsnag.com/

Consistent

B
TLS Certificate Expiry & Recommendations
178 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

178
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
B
CDN & Delivery
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
REVIEW
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: CDG52-P3)
Got: x-amz-cf-id: veoPaipN7Mutd18X_Xr4bk1Wghhrbul_JO2M1NXyyIyVCjcWl_SNtQ==
Info::
CDN cache status: FunctionGeneratedResponse from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status FunctionGeneratedResponse from cloudfront Evidence x-amz-cf-id: veoPaipN7Mutd18X_Xr4bk1Wghhrbul_JO2M1NXyyIyVCjcWl_SNtQ==
A+
DNS Records
4 A records, 40 ms lookup
PASS
4 A records, 40 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 3.165.136.17, 3.165.136.27, 3.165.136.114, 3.165.136.3
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1651.awsdns-14.co.uk, ns-311.awsdns-38.com, ns-1240.awsdns-27.org, ns-974.awsdns-57.net
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 40 ms
Got: 40 ms
A3.165.136.17, 3.165.136.27, 3.165.136.114, 3.165.136.3
AAAA
CNAME
NSns-1651.awsdns-14.co.uk, ns-311.awsdns-38.com, ns-1240.awsdns-27.org, ns-974.awsdns-57.net
MX
10 us-smtp-inbound-2.mimecast.com
10 us-smtp-inbound-1.mimecast.com
TXT
atlassian-domain-verification=LT8w16bpRN1jQLkO+Hi4fVyWjItQAqJA+oZcx02AOuk8kEsBpM...
google-site-verification=S8hSZCU-dY0ArbvB7hF8NGGEtVnzTL7pKnxyzPZYjjU
google-site-verification=IN4EdTbQ2u1llbrrZ2C4l27LPSmQLsLd_dZZ8XV0F4o
SPF v=spf1 include:amazonses.com include:mktomail.com include:spf.protection.outlook...
MS=5E694005809BF98FFFFCEF9960730174EE04A592
mimecast=0ed1fe018afb28a799336744a1b654b945b999b786
_y530x26l6masg9heypfx2yjnbrtzyt4
MS=ms51150029
CAALookup not available with standard resolver
Resolved in 40 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.

A
Redirect Chain
1 redirect(s), 189 ms total
PASS
1 redirect(s), 189 ms total
Info::
Single redirect
Got: https://bugsnag.com → https://www.bugsnag.com/ (301)
Info::
WWW normalization redirect

https://bugsnag.com

54 ms · HTTP/1.1

301

https://www.bugsnag.com/

135 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bugsnag.com30154 msHTTP/1.1CloudFront
2https://www.bugsnag.com/200135 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A
Crawlability
no robots.txt, sitemap with 24 URLs
PASS
no robots.txt, sitemap with 24 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 24 entries

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

A+
Domain Intelligence
bugsnag.com — via Gandi SAS, 14 years, 10 months old, hosted on AWS
PASS
bugsnag.com — via Gandi SAS, 14 years, 10 months old, hosted on AWS
Info::
Domain registered until Aug 18, 2027 (1 years, 4 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: Gandi SAS
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

400 days

August 18, 2027

SSL certificate

178 days

Issued by DigiCert Inc

Domain age

14 years, 10 months

Registered August 18, 2011

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

3.165.136.114

Registrar

Gandi SAS

Unlocked 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Gandi SAS
Created August 18, 2011 (14 years, 10 months ago)
Expires August 18, 2027 (1 years, 4 months)
Last Updated June 11, 2025
Name Servers ns-1240.awsdns-27.org, ns-1651.awsdns-14.co.uk, ns-311.awsdns-38.com, ns-974.awsdns-57.net
DNSSEC Not enabled
Hosting
IP Address 3.165.136.114
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
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

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.

Why this matters

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

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

Connection waterfall

DNS Lookup 32 ms TCP Connect 16 ms TLS Handshake 21 ms Server Processing 21 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback