Skip to content
https://swagger.io

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 3 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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

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

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • 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
2 A records, 45 ms lookup
PASS
2 A records, 45 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 162.159.140.69, 172.66.0.69
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-725.awsdns-26.net, ns-1991.awsdns-56.co.uk, ns-266.awsdns-33.com, ns-1077.awsdns-06.org
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: 45 ms
Got: 45 ms
A162.159.140.69, 172.66.0.69
AAAA
CNAME
NSns-725.awsdns-26.net, ns-1991.awsdns-56.co.uk, ns-266.awsdns-33.com, ns-1077.awsdns-06.org
MX
0 us-smtp-inbound-1.mimecast.com
10 us-smtp-inbound-2.mimecast.com
TXT
google-site-verification=ADwb7r6XTIZqavtEaI_QSKb0zD9nNlWuE7-e-Z2eOCA
detectify-verification=8ed6429e219678f4eb827c47022baa9b
ahrefs-site-verification_1d2c1c43e1d55985da2e06feddacc88fbb8c041d9db1b94a72fe737...
SPF v=spf1 a mx include:spf.protection.outlook.com include:us._netblocks.mimecast.co...
CAALookup not available with standard resolver
Resolved in 45 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://swagger.io

https://swagger.io

639 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://swagger.io200639 msHTTP/1.1cloudflare
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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.swagger.io/
200https://swagger.io/

Preferred variant: non-www

HTTP → HTTPS

301http://swagger.io/ https://swagger.io/

Consistent

A+
Domain Intelligence
swagger.io — via GoDaddy.com, LLC, 11 years, 11 months old, hosted on Cloudflare
PASS
swagger.io — via GoDaddy.com, LLC, 11 years, 11 months old, hosted on Cloudflare
Info::
Domain registered until Jul 19, 2030 (4 years, 3 months remaining)
Info::
Registrar: GoDaddy.com, LLC
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

1497 days

July 19, 2030

SSL certificate

46 days

Issued by Google Trust Services

Domain age

11 years, 11 months

Registered July 19, 2014

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

162.159.140.69

Registrar

GoDaddy.com, LLC

Locked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar GoDaddy.com, LLC
Created July 19, 2014 (11 years, 11 months ago)
Expires July 19, 2030 (4 years, 3 months)
Last Updated September 2, 2025
Name Servers ns-1077.awsdns-06.org, ns-1991.awsdns-56.co.uk, ns-725.awsdns-26.net, ns-266.awsdns-33.com
Registrant Domains By Proxy, LLC
Hosting
IP Address 162.159.140.69
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: whois (1.2s)

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

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

Connection waterfall

DNS Lookup 30 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 583 ms Content Transfer 111 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f08707f1c0415de-CDG
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f08707f1c0415de-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback