Skip to content
https://daelimbelefic.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from Amsterdam, Netherlands
200 OK
Checks
17
8 PASS 9 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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 141.193.213.11: lookup 141.193.213.11: 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.
C
Multi-Resolver DNS Speed
Action
Mean 248ms across 3 resolvers (spread 127ms)
REVIEW
Mean 248ms across 3 resolvers (spread 127ms)
Info::
Cloudflare: 198ms
Got: 198ms via 1.1.1.1:53
Info::
Quad9: 223ms
Got: 223ms via 9.9.9.9:53
Info::
Google: 325ms
Got: 325ms via 8.8.8.8:53
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
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 429 Expected: 301 redirect to HTTPS

www / non-www

301https://www.daelimbelefic.com/
200https://daelimbelefic.com/

Preferred variant: non-www

HTTP → HTTPS

429http://daelimbelefic.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • 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
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: 429, /health: 429, /healthz: 429, /ping: 429, /status: 429.
A
DNS Records
1 A records, 784 ms lookup
PASS
1 A records, 784 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 141.193.213.11
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: dns14.hichina.com, dns13.hichina.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (784 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 784 ms
A141.193.213.11
AAAA
CNAME
NSdns14.hichina.com, dns13.hichina.com
MX
10 mx.zoho.com
20 mx2.zoho.com
50 mx3.zoho.com
TXT
zoho-verification=zb77342468.zmverify.zoho.com.cn
google-site-verification=3DlQxcTNjC4njCkV9XC3znu5ZAklERVjDVyXLOcfqEI
SPF v=spf1 include:one.zoho.com ~all
zoho-verification=7F08Z2DLN4.zmverify.zoho.com.cn
CAALookup not available with standard resolver
Resolved in 784 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

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://daelimbelefic.com

https://daelimbelefic.com

479 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://daelimbelefic.com200479 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 239 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 239 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
Crawl-delay: 10
Sitemap: https://daelimbelefic.com/sitemaps.xml
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://daelimbelefic.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
A+
Domain Intelligence
daelimbelefic.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 6 years, 10 months old, hosted on Cloudflare
PASS
daelimbelefic.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 6 years, 10 months old, hosted on Cloudflare
Info::
Domain registered until Dec 9, 2032 (6 years, 4 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: Alibaba Cloud Computing (Beijing) Co., Ltd.
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: Cloudflare
Got: AS209242
Domain expiry

2288 days

December 9, 2032

SSL certificate

72 days

Issued by Let's Encrypt

Domain age

6 years, 10 months

Registered December 9, 2019

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS209242

141.193.213.11

Registrar

Alibaba Cloud Computing (Beijing) Co., Ltd.

Unlocked 2 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 Alibaba Cloud Computing (Beijing) Co., Ltd.
Created December 9, 2019 (6 years, 10 months ago)
Expires December 9, 2032 (6 years, 4 months)
Last Updated September 12, 2025
Name Servers dns13.hichina.com, dns14.hichina.com
DNSSEC Not enabled
Hosting
IP Address 141.193.213.11
ASN AS209242 (CLOUDFLARESPECTRUM - Cloudflare London, LLC, US)
Provider Cloudflare
Data source: rdap (1.1s)

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

Connection waterfall

DNS Lookup 416 ms TCP Connect 1 ms TLS Handshake 12 ms Server Processing 13 ms Content Transfer 2 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: AMS)
Got: cf-ray: a359850368b1e4bc-AMS
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: a359850368b1e4bc-AMS
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 3 header(s)
Got: age=1996845, cf-cache-status=HIT, x-cache=MISS
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback