Skip to content
https://kiva.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 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
Crawlability
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 709 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 709 B Sitemaps referenced 1 User-agents SemrushBot, PetalBot, * Blocking No — crawling allowed
User-agent: *

# Login pages
Disallow: /authenticate
Disallow: /error
Disallow: /last_login
Disallow: /login
Disallow: /logout
Disallow: /oauth
Disallow: /register
Disallow: /ui-login
Disallow: /ui-logout

# Checkout pages
Disallow: /basket
Disallow: /checkout
Disallow: /thanks

# Common pages requiring login
Disallow: /account
Disallow: /admin
Disallow: /ajax
Disallow: /myLenderId
Disallow: /portfolio
Disallow: /settings
Disallow: /updates/myloans
Disallow: /withdraw

# Other
Disallow: /app.php
Disallow: /i/
Disallow: /*?*pageID=
Disallow: /teams/*/loans
Disallow: /teams/join/*

User-agent: SemrushBot
Crawl-delay: 60

User-agent: PetalBot
Disallow: /

Sitemap: http://www.kiva.org/sitemaps/index.xml

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
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.kiva.org/
200https://kiva.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://kiva.org/ https://kiva.org:443/

Consistent

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

Certificate validity

262
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
  • 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
A+
DNS Records
3 A records, 123 ms lookup
PASS
3 A records, 123 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 54.186.201.26, 52.38.154.163, 35.80.154.100
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1401.awsdns-47.org, ns-467.awsdns-58.com, ns-823.awsdns-38.net, ns-1628.awsdns-11.co.uk
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: 123 ms
Got: 123 ms
A54.186.201.26, 52.38.154.163, 35.80.154.100
AAAA
CNAME
NSns-1401.awsdns-47.org, ns-467.awsdns-58.com, ns-823.awsdns-38.net, ns-1628.awsdns-11.co.uk
MX
10 aspmx.l.google.com
20 alt2.aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 aspmx2.googlemail.com
30 aspmx3.googlemail.com
TXT
facebook-domain-verification=6k9ebdtev0wfu1xrh5uuy0a898natq
ZOOM_verify_EG8dulX8TLC_IA_EcCClOw
onetrust-domain-verification=7d515025ceee4735a290af3918d6eab1
openai-domain-verification=dv-yC2ze882C9VikO8gNy93jlRg
google-site-verification=K6pOshF2tXM_Od3Aox6x0D5NCifEGgjeoKpEgm_0FnA
pinterest-site-verification=5d85d0a1883817322133a4b593943825
adobe-idp-site-verification=6fe80722ea29c9a5df78b8cc8395beef437166b62246b1ae0f96...
google-site-verification=5jYUB2vDYFFMq4m_24JfhaRstDUUtCWM-YDQmyeNudE
SPF v=spf1 ip4:50.31.62.59 ip4:149.72.59.130 ip4:44.231.14.47 ip4:44.228.3.254 ip4:9...
MS=ms86669204
google-site-verification=aNSEEHIDfPXNUeb67q8FOy1leF8IHP3my5W5P-K3Ras
google-site-verification=_Xv5McueunM-dPmSF1ge6wsY8FVJq0aPt_pcDKaeBm4
google-site-verification=OC0AuKwkDfkZPB9fFbcQic9Sy0BEzHiJ_oiOtUH13lE
google-site-verification=R376pH2Qg1DF_VAUNVoD9UdHnYQZgJc58a0RuOZBRJo
google-site-verification=dw2XUoLh5GVnlVttqOWbFXhrDjOlJBhhPZ2eYZmoUPY
have-i-been-pwned-verification=db1636b384f9357d05e558bf19131b1c
apple-domain-verification=aMzQxkiCFjcw6qs2
6v2dgkhyvf59rskdrvnftbk323znlwlh
google-site-verification=p8xG9TMPbQbi9nZd95YSxllHvJAD67-tqmHpAhXImIk
atlassian-domain-verification=OVxK2M7RNrqHbkHkbj5fgLMB7PskfmIGG/vuJOF56EfSoZwcEO...
google-site-verification=1fC3FgT5ECns8re10uYmOP6ti515lHow0590LexLpZI
CAALookup not available with standard resolver
Resolved in 123 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
1 redirect(s), 951 ms total
PASS
1 redirect(s), 951 ms total
Info::
Single redirect
Got: https://kiva.org → https://www.kiva.org:443/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 951 ms total
Got: 951 ms

https://kiva.org

707 ms · HTTP/1.1

301

https://www.kiva.org:443/

245 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://kiva.org301707 msHTTP/1.1awselb/2.0
2https://www.kiva.org:443/200245 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
kiva.org — via GoDaddy.com, LLC, 24 years, 4 months old, hosted on AWS
PASS
kiva.org — via GoDaddy.com, LLC, 24 years, 4 months old, hosted on AWS
Info::
Domain registered until Apr 2, 2028 (1 years, 11 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: GoDaddy.com, LLC
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: AWS
Got: AS16509
Domain expiry

657 days

April 2, 2028

SSL certificate

262 days

Issued by Amazon

Domain age

24 years, 4 months

Registered April 2, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

35.80.154.100

Registrar

GoDaddy.com, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created April 2, 2002 (24 years, 4 months ago)
Expires April 2, 2028 (1 years, 11 months)
Last Updated April 8, 2026
Name Servers ns-1401.awsdns-47.org, ns-1628.awsdns-11.co.uk, ns-467.awsdns-58.com, ns-823.awsdns-38.net
DNSSEC Not enabled
Hosting
IP Address 35.80.154.100
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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

Connection waterfall

DNS Lookup 46 ms TCP Connect 180 ms TLS Handshake 361 ms Server Processing 182 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