Skip to content
https://www.the-fund.ae

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
6
PASS
11
INFO
0
Probed from Madrid, Spain
302 Found
Checks
17
11 PASS 6 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
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.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 188.114.97.2: lookup 188.114.97.2: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 188.114.96.2: lookup 188.114.96.2: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2a06:98c1:3121::2: lookup 2a06:98c1:3121::2: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2a06:98c1:3120::2: lookup 2a06:98c1:3120::2: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
TLS Certificate Expiry & Recommendations
63 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
2 A records, 34 ms lookup
PASS
2 A records, 34 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 188.114.97.2, 188.114.96.2
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3121::2, 2a06:98c1:3120::2
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 34 ms
Got: 34 ms
A188.114.97.2, 188.114.96.2
AAAA2a06:98c1:3121::2, 2a06:98c1:3120::2
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 34 ms

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 22ms across 3 resolvers (spread 11ms)
PASS
Mean 22ms across 3 resolvers (spread 11ms)
Info::
Cloudflare: 17ms
Got: 17ms via 1.1.1.1:53
Info::
Quad9: 23ms
Got: 23ms via 9.9.9.9:53
Info::
Google: 28ms
Got: 28ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 227 ms total
PASS
1 redirect(s), 227 ms total
Info::
Single redirect
Got: https://www.the-fund.ae → https://www.the-fund.ae/en (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.the-fund.ae

https://www.the-fund.ae

139 ms · HTTP/1.1

302

https://www.the-fund.ae/en

89 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.the-fund.ae302139 msHTTP/1.1cloudflare
2https://www.the-fund.ae/en20089 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:3121::2, 2a06:98c1:3120::2
Got: 17 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:3121::2, 2a06:98c1:3120::2 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 13 URLs
PASS
robots.txt present, sitemap with 13 URLs
Info::
robots.txt is present
Got: 1175 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 13 entries
Info::
Sitemap index with 13 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1175 B Sitemaps referenced 1 User-agents KeenableBot, DataForSeoBot, MJ12bot, Baiduspider, cohere-ai, Reflectionbot, Amzn-SearchBot, ChatGPT-User, OAI-SearchBot, Anthropic-AI, YouBot, Diffbot, SemrushBot, Amazonbot, CCBot, Applebot-Extended, AionBot, ShapBot, LinkupBot, ExaSearchBot, Barkrowler, Claude-Web, AhrefsBot, *, GPTBot, ClaudeBot, Bytespider, DotBot, SERankingBacklinksBot, PetalBot, Google-Extended, PerplexityBot, meta-externalagent Blocking No — crawling allowed
User-Agent: *
Allow: /
Allow: /api/og
Allow: /api/asset-logo
Disallow: /api/
Disallow: /_next/data/
Disallow: /admin/
Disallow: /*_rsc=

User-Agent: GPTBot
User-Agent: ChatGPT-User
User-Agent: OAI-SearchBot
User-Agent: Claude-Web
User-Agent: Anthropic-AI
User-Agent: Google-Extended
User-Agent: PerplexityBot
User-Agent: YouBot
User-Agent: Diffbot
User-Agent: cohere-ai
User-Agent: Applebot-Extended
User-Agent: SemrushBot
User-Agent: AhrefsBot
Allow: /
Disallow: /api/
Disallow: /_next/data/
Disallow: /admin/
Disallow: /*_rsc=
Disallow: /en/invest/stocks/compare
Disallow: /en/invest/etfs/compare
Disallow: /ar/invest/stocks/compare
Disallow: /ar/invest/etfs/compare

User-Agent: ClaudeBot
User-Agent: Amazonbot
User-Agent: Amzn-SearchBot
User-Agent: CCBot
User-Agent: meta-externalagent
User-Agent: Bytespider
User-Agent: AionBot
User-Agent: ShapBot
User-Agent: Reflectionbot
User-Agent: LinkupBot
User-Agent: KeenableBot
User-Agent: ExaSearchBot
User-Agent: DataForSeoBot
User-Agent: MJ12bot
User-Agent: DotBot
User-Agent: SERankingBacklinksBot
User-Agent: Barkrowler
User-Agent: PetalBot
User-Agent: Baiduspider
Disallow: /

Sitemap: https://www.the-fund.ae/sitemap.xml

A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Warning::
HTTP→HTTPS redirect is not permanent
Got: HTTP 302 Expected: 301 or 308 permanent redirect

www / non-www

200https://www.the-fund.ae/
302https://the-fund.ae/

Preferred variant: www

HTTP → HTTPS

302http://www.the-fund.ae/ → https://www.the-fund.ae/

Use a permanent redirect (301 or 308) instead of a temporary one

A+
Domain Intelligence
the-fund.ae — via AESERVER
PASS
the-fund.ae — via AESERVER
Info::
Registrar: AESERVER
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.
Domain expiry

Unknown

SSL certificate

63 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a06:98c1:3120::2

Registrar

AESERVER

Unlocked 2 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar AESERVER
Name Servers naomi.ns.cloudflare.com, wesley.ns.cloudflare.com
Registrant Fintum Market Intelligence GmbH
Hosting
IP Address 2a06:98c1:3120::2
Data source: whois (0.6s)

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 196 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.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
29 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
196 ms
Total Time Total request time from DNS lookup through full response.
197 ms

Connection waterfall

DNS Lookup 37 ms TCP Connect 17 ms TLS Handshake 29 ms Server Processing 114 ms Content Transfer 0 ms
A
CDN & Delivery
Document and assets on Cloudflare
PASS
Document and assets on Cloudflare
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a54aa8d87eccd619-CDG
Info::
CDN cache status: DYNAMIC
Info::
Assets on Cloudflare: data-api.el-fondo.com (assets: 17), cache HIT
Got: cf-ray: a54aaab11daa3c9e-CDG
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a54aa8d87eccd619-CDG

Asset hosts on a CDN

  • data-api.el-fondo.com — Cloudflare · assets: 17 · Cache Status: HIT
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback