Skip to content
https://fundable.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
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.

B
Redirect Chain
1 redirect(s), 1144 ms total
REVIEW
1 redirect(s), 1144 ms total
Info::
Single redirect
Got: https://fundable.com → https://www.fundable.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1144 ms total
Got: 1144 ms

https://fundable.com

401 ms · HTTP/1.1

301

https://www.fundable.com/

743 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://fundable.com301401 msHTTP/1.1Apache/2.4.18 (Ubuntu)
2https://www.fundable.com/200743 msHTTP/1.1Apache/2.4.18 (Ubuntu)

See the visual redirect chain in the HTTP Probe tab →

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.fundable.com/
200https://fundable.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://fundable.com/ https://www.fundable.com/

Consistent

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

Certificate validity

251
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
6 A records, 55 ms lookup
PASS
6 A records, 55 ms lookup
Info::
Resolves to 6 IPv4 address(es)
Got: 44.222.44.131, 100.52.3.222, 52.1.232.117, 3.211.58.213, 50.19.200.20, 34.231.105.222
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1475.awsdns-56.org, ns-733.awsdns-27.net, ns-317.awsdns-39.com, ns-1649.awsdns-14.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: 55 ms
Got: 55 ms
A44.222.44.131, 100.52.3.222, 52.1.232.117, 3.211.58.213, 50.19.200.20, 34.231.105.222
AAAA
CNAME
NSns-1475.awsdns-56.org, ns-733.awsdns-27.net, ns-317.awsdns-39.com, ns-1649.awsdns-14.co.uk
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
SPF v=spf1 include:_spf.google.com include:sendgrid.net include:459884.spf05.hubspot...
google-site-verification=yWey_DZb6epAm1rGXkNThPg4vl8whIySzQGXTOx5xRU
google-site-verification=gNdbxNq5Ms5tejgY7BAoUUWIa7bSFLtKxbWODc1ziOw
CAALookup not available with standard resolver
Resolved in 55 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+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 59 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 59 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Sitemap: https://www.fundable.com/sitemap.xml
A+
Domain Intelligence
fundable.com — via GoDaddy.com, LLC, 22 years old, hosted on AWS
PASS
fundable.com — via GoDaddy.com, LLC, 22 years old, hosted on AWS
Info::
Domain registered until Aug 9, 2026 (3 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: AS14618
Domain expiry

57 days

August 9, 2026

SSL certificate

251 days

Issued by Amazon

Domain age

22 years

Registered August 9, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

34.231.105.222

Registrar

GoDaddy.com, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created August 9, 2004 (22 years ago)
Expires August 9, 2026 (3 months)
Last Updated August 10, 2025
Name Servers ns-1475.awsdns-56.org, ns-1649.awsdns-14.co.uk, ns-317.awsdns-39.com, ns-733.awsdns-27.net
DNSSEC Not enabled
Hosting
IP Address 34.231.105.222
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 57 ms TCP Connect 97 ms TLS Handshake 196 ms Server Processing 106 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