Skip to content
https://ONIXLabs.io

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
8
PASS
8
INFO
1
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
8 PASS 8 REVIEW
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/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR for 185.199.111.153 does not match any cert SAN: cdn-185-199-111-153.github.com
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 for 185.199.110.153 does not match any cert SAN: cdn-185-199-110-153.github.com
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 for 185.199.108.153 does not match any cert SAN: cdn-185-199-108-153.github.com
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 for 185.199.109.153 does not match any cert SAN: cdn-185-199-109-153.github.com
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.
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
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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.ONIXLabs.io/
200https://ONIXLabs.io/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ONIXLabs.io/ → https://www.onixlabs.io/

Consistent

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

Certificate validity

75
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
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
4 A records, 39 ms lookup
PASS
4 A records, 39 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 185.199.111.153, 185.199.110.153, 185.199.108.153, 185.199.109.153
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: dns1.registrar-servers.com, dns2.registrar-servers.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 39 ms
Got: 39 ms
A185.199.111.153, 185.199.110.153, 185.199.108.153, 185.199.109.153
AAAA—
CNAME—
NSdns1.registrar-servers.com, dns2.registrar-servers.com
MX
10 mx2.privateemail.com
10 mx1.privateemail.com
TXT
google-site-verification=Xqap6XamyCwWwLlTghPUhKuLBkY_8LNl56txxWwmgaM
SPF v=spf1 include:spf.privateemail.com ~all
CAALookup not available with standard resolver
Resolved in 39 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (ECDSAP256SHA256)
A+
Multi-Resolver DNS Speed
Mean 17ms across 3 resolvers (spread 20ms)
PASS
Mean 17ms across 3 resolvers (spread 20ms)
Info::
Quad9: 5ms
Got: 5ms via 9.9.9.9:53
Info::
Cloudflare: 23ms
Got: 23ms via 1.1.1.1:53
Info::
Google: 25ms
Got: 25ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 221 ms total
PASS
1 redirect(s), 221 ms total
Info::
Single redirect
Got: https://ONIXLabs.io → https://www.onixlabs.io/ (301)
Info::
WWW normalization redirect

https://ONIXLabs.io

6 ms · HTTP/1.1

301

https://www.onixlabs.io/

215 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ONIXLabs.io3016 msHTTP/1.1GitHub.com
2https://www.onixlabs.io/200215 msHTTP/1.1GitHub.com

See the visual redirect chain in the HTTP Probe tab →

A+
HTTP Probe Timing
Total 180 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
38 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.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
180 ms
Total Time Total request time from DNS lookup through full response.
180 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 0 ms TLS Handshake 4 ms Server Processing 137 ms Content Transfer 0 ms
A
CDN & Delivery
Document on Fastly; assets also on GitHub Pages
PASS
Document on Fastly; assets also on GitHub Pages
Info::
Document is served via Fastly CDN (edge: TOJ)
Got: x-fastly-request-id: aa8ea0086b4aff91572604539b4499761fb19eac
Info::
CDN cache status: MISS
Info::
Assets on GitHub Pages: www.onixlabs.io (assets: 42), cache HIT
Got: delegation onix-labs.github.io
Document served via CDN: Fastly
Provider Fastly Cache Status MISS Evidence x-fastly-request-id: aa8ea0086b4aff91572604539b4499761fb19eac

Asset hosts on a CDN

  • www.onixlabs.io — GitHub Pages · assets: 42 · Cache Status: HIT
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 4 header(s)
Got: age=0, x-cache=MISS, x-cache-hits=0, x-served-by=cache-toj-leto2350043-TOJ
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback