Skip to content
https://wireboard.io

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
1
REVIEW
5
PASS
11
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
11 PASS 5 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 49.12.16.84 does not match any cert SAN: static.84.16.12.49.clients.your-server.de
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR lookup failed for 2a01:4f8:c011:1::1: lookup 2a01:4f8:c011:1::1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
TLS Certificate Expiry & Recommendations
81 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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 Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
A+
DNS Records
1 A records, 51 ms lookup
PASS
1 A records, 51 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 49.12.16.84
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a01:4f8:c011:1::1
Info::
3 nameserver(s) configured
Got: ns2.digitalocean.com, ns1.digitalocean.com, ns3.digitalocean.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 51 ms
Got: 51 ms
A49.12.16.84
AAAA2a01:4f8:c011:1::1
CNAME—
NSns2.digitalocean.com, ns1.digitalocean.com, ns3.digitalocean.com
MX
5 mta-gw.infomaniak.ch
TXT
google-site-verification=mwB8frJ2ZaqgnU4L9Flxnz8UDHrE8tiznvB2C_7BbY0
newsletter.infomaniak.com
SPF v=spf1 include:spf.infomaniak.ch -all
CAALookup not available with standard resolver
Resolved in 51 ms

Multiple A records provide failover if one server goes down.

Why this matters

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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 42ms across 3 resolvers (spread 17ms)
PASS
Mean 42ms across 3 resolvers (spread 17ms)
Info::
Quad9: 33ms
Got: 33ms via 9.9.9.9:53
Info::
Google: 44ms
Got: 44ms via 8.8.8.8:53
Info::
Cloudflare: 50ms
Got: 50ms via 1.1.1.1:53
A
Redirect Chain
1 redirect(s), 262 ms total
PASS
1 redirect(s), 262 ms total
Info::
Single redirect
Got: https://wireboard.io → https://wireboard.io/en (301)

https://wireboard.io

130 ms · HTTP/1.1

301

https://wireboard.io/en

132 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://wireboard.io301130 msHTTP/1.1
2https://wireboard.io/en200132 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (29 ms)
PASS
IPv6 reachable (29 ms)
Info::
IPv6 is configured and reachable at 2a01:4f8:c011:1::1
Got: 29 ms connect
IPv6 Ready
AAAA Records 2a01:4f8:c011:1::1 Connection Reachable (29 ms)
A+
Crawlability
robots.txt present, sitemap with 754 URLs
PASS
robots.txt present, sitemap with 754 URLs
Info::
robots.txt is present
Got: 114 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 754 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 114 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
Sitemap: https://wireboard.io/sitemap.xml
Sitemap: https://wireboard.io/blog_sitemap.xml

User-agent: *
Disallow:
sitemap.xml 200 OK
Type URL Set URLs 754 entries Valid XML Yes
Sample URLs:
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)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

308http://wireboard.io/ → https://wireboard.io

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
wireboard.io — via Infomaniak Network SA, 7 years old
PASS
wireboard.io — via Infomaniak Network SA, 7 years old
Info::
Domain registered until May 22, 2027 (1 years remaining)
Info::
Registrar: Infomaniak Network SA
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Domain expiry

372 days

May 22, 2027

SSL certificate

81 days

Issued by Let's Encrypt

Domain age

7 years

Registered May 22, 2019

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a01:4f8:c011:1::1

Registrar

Infomaniak Network SA

Locked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar Infomaniak Network SA
Created May 22, 2019 (7 years ago)
Expires May 22, 2027 (1 years)
Last Updated March 29, 2026
Name Servers ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
Registrant SwissOps Saarl
Hosting
IP Address 2a01:4f8:c011:1::1
Data source: whois (0.9s)

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

Connection waterfall

DNS Lookup 44 ms TCP Connect 29 ms TLS Handshake 33 ms Server Processing 53 ms Content Transfer 0 ms
A+
Operational Status Page
Status page detected via hosted platform (statuspage.io)
PASS
Status page detected via hosted platform (statuspage.io)
Info::
Status page link found: https://wireboard.statuspage.io
Got: https://wireboard.statuspage.io
A+
Health Check Endpoint
Health endpoint at https://wireboard.io/healthz (HTTP 200)
PASS
Health endpoint at https://wireboard.io/healthz (HTTP 200)
Info::
Public health endpoint at https://wireboard.io/healthz
Got: https://wireboard.io/healthz
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback