Skip to content
https://koalapic.com/en/

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
5
PASS
11
INFO
0
Probed from Madrid, Spain
200 OK
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
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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 51.210.209.19 does not match any cert SAN: ns3179604.ip-51-210-209.eu
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
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.koalapic.com/en/
200https://koalapic.com/en/

Inconsistent — duplicate content risk

Trailing Slash

200https://koalapic.com/en/
301https://koalapic.com/en

HTTP → HTTPS

301http://koalapic.com/en/ → https://koalapic.com/en/

Consistent

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 46 ms lookup
PASS
1 A records, 46 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 51.210.209.19
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns110.ovh.net, dns110.ovh.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 46 ms
Got: 46 ms
A51.210.209.19
AAAA—
CNAME—
NSns110.ovh.net, dns110.ovh.net
MX
0 mail.appscyborg.com
TXT
SPF v=spf1 mx -all
CAALookup not available with standard resolver
Resolved in 46 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+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (RSASHA256)
A+
Multi-Resolver DNS Speed
Mean 36ms across 3 resolvers (spread 41ms)
PASS
Mean 36ms across 3 resolvers (spread 41ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 28ms
Got: 28ms via 1.1.1.1:53
Info::
Quad9: 61ms
Got: 61ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://koalapic.com/en/

https://koalapic.com/en/

109 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://koalapic.com/en/200109 msHTTP/1.1nginx
A
Crawlability
no robots.txt, sitemap with 1209 URLs
PASS
no robots.txt, sitemap with 1209 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 1209 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.

sitemap.xml 200 OK
Type URL Set URLs 1209 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
koalapic.com — via OVH sas, 6 months old, hosted on OVH
PASS
koalapic.com — via OVH sas, 6 months old, hosted on OVH
Info::
Domain registered until Feb 12, 2027 (5 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: OVH 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: OVH
Got: AS16276
Domain expiry

170 days

February 12, 2027

SSL certificate

41 days

Issued by Let's Encrypt

Domain age

6 months

Registered February 12, 2026

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

51.210.209.19

Registrar

OVH sas

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar OVH sas
Created February 12, 2026 (6 months ago)
Expires February 12, 2027 (5 months)
Last Updated February 12, 2026
Name Servers dns110.ovh.net, ns110.ovh.net
DNSSEC Enabled
Hosting
IP Address 51.210.209.19
ASN AS16276 (OVH - OVH SAS, FR)
Provider OVH
Data source: rdap (0.5s)

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

Connection waterfall

DNS Lookup 42 ms TCP Connect 19 ms TLS Handshake 24 ms Server Processing 65 ms Content Transfer 2 ms
A+
CDN Cache Observability
Cache state: Age=12s
PASS
Cache state: Age=12s
Info::
CDN cache state observable via 1 header(s)
Got: age=12
A+
Operational Status Page
Status page detected via anchor text
PASS
Status page detected via anchor text
Info::
Status page link found: /en/status/
Got: /en/status/
A+
Health Check Endpoint
Health endpoint at https://koalapic.com/healthz (HTTP 200)
PASS
Health endpoint at https://koalapic.com/healthz (HTTP 200)
Info::
Public health endpoint at https://koalapic.com/healthz
Got: https://koalapic.com/healthz
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback