Skip to content
https://kuula.co

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
5 PASS 3 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.

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.kuula.co/
200https://kuula.co/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://kuula.co/ → https://kuula.co:443/

Consistent

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
A+
DNS Records
3 A records, 34 ms lookup
PASS
3 A records, 34 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 63.179.32.142, 35.159.252.148, 18.196.85.119
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-649.awsdns-17.net, ns-1751.awsdns-26.co.uk, ns-358.awsdns-44.com, ns-1299.awsdns-34.org
Info::
5 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: 34 ms
Got: 34 ms
A63.179.32.142, 35.159.252.148, 18.196.85.119
AAAA—
CNAME—
NSns-649.awsdns-17.net, ns-1751.awsdns-26.co.uk, ns-358.awsdns-44.com, ns-1299.awsdns-34.org
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
google-site-verification=2l1TJ1ipgYpPYibCUyxWsspkKyzyz5rLN5xsxiwizzk
SPF v=spf1 mx a include:_spf.google.com include:amazonses.com include:compute.amazon...
CAALookup not available with standard resolver
Resolved in 34 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://kuula.co

https://kuula.co

136 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://kuula.co200136 msHTTP/1.1Apache/2.4.52 (Ubuntu)
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 134 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 134 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

User-agent: *
Disallow: /api/
Disallow: /templates/
Disallow: /edit/
Disallow: /settings/
Sitemap: https://kuula.co/sitemap/index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
kuula.co — via 1API GmbH, 10 years, 4 months old, hosted on AWS
PASS
kuula.co — via 1API GmbH, 10 years, 4 months old, hosted on AWS
Info::
Domain registered until Feb 10, 2027 (9 months remaining)
Info::
Registrar: 1API GmbH
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

240 days

February 10, 2027

SSL certificate

61 days

Issued by Amazon

Domain age

10 years, 4 months

Registered February 11, 2016

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

63.179.32.142

Registrar

1API GmbH

Locked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar 1API GmbH
Created February 11, 2016 (10 years, 4 months ago)
Expires February 10, 2027 (9 months)
Last Updated March 1, 2026
Name Servers ns-649.awsdns-17.net, ns-1299.awsdns-34.org, ns-1751.awsdns-26.co.uk, ns-358.awsdns-44.com
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 63.179.32.142
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (1.1s)

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

Connection waterfall

DNS Lookup 37 ms TCP Connect 31 ms TLS Handshake 64 ms Server Processing 38 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