Skip to content
http://kepalabergetar3k.cfd

Infrastructure

· 16 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
7
PASS
9
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
16
9 PASS 7 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.
B
Reverse DNS
4 PTR record(s) found (no cert data to match against)
REVIEW
4 PTR record(s) found (no cert data to match against)
Info::
PTR lookup failed for 188.114.97.0: lookup 188.114.97.0: no such host
Info::
PTR lookup failed for 188.114.96.0: lookup 188.114.96.0: no such host
Info::
PTR lookup failed for 2a06:98c1:3121::: lookup 2a06:98c1:3121::: no such host
Info::
PTR lookup failed for 2a06:98c1:3120::: lookup 2a06:98c1:3120::: no such host
B
Redirect Chain
1 redirect(s), 2275 ms total
REVIEW
1 redirect(s), 2275 ms total
Info::
Single redirect
Got: http://kepalabergetar3k.cfd → https://kepalabergetar3k.cfd/ (301)
Info::
HTTP to HTTPS redirect present
Warning::
Redirect overhead: 2275 ms total
Got: 2275 ms

http://kepalabergetar3k.cfd

1057 ms · HTTP/1.1

301

https://kepalabergetar3k.cfd/

1218 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1http://kepalabergetar3k.cfd3011057 msHTTP/1.1cloudflare
2https://kepalabergetar3k.cfd/2001218 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: AMS)
Got: cf-ray: a366d3aac9e2f5f2-AMS
Document served via CDN: Cloudflare
Provider Cloudflare Evidence cf-ray: a366d3aac9e2f5f2-AMS
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
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.
A+
DNS Records
2 A records, 25 ms lookup
PASS
2 A records, 25 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 188.114.97.0, 188.114.96.0
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3121::, 2a06:98c1:3120::
Info::
2 nameserver(s) configured
Got: demi.ns.cloudflare.com, frank.ns.cloudflare.com
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: 25 ms
Got: 25 ms
A188.114.97.0, 188.114.96.0
AAAA2a06:98c1:3121::, 2a06:98c1:3120::
CNAME
NSdemi.ns.cloudflare.com, frank.ns.cloudflare.com
MX
TXT
CAALookup not available with standard resolver
Resolved in 25 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 11ms across 3 resolvers (spread 17ms)
PASS
Mean 11ms across 3 resolvers (spread 17ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Quad9: 8ms
Got: 8ms via 9.9.9.9:53
Info::
Google: 21ms
Got: 21ms via 8.8.8.8:53
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:3121::, 2a06:98c1:3120::
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:3121::, 2a06:98c1:3120:: Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 178 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
Sitemap index with 6 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 178 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://kepalabergetar3k.cfd/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
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: non-www)

www / non-www

301http://www.kepalabergetar3k.cfd/
200http://kepalabergetar3k.cfd/

Preferred variant: non-www

A+
Domain Intelligence
kepalabergetar3k.cfd — via Spaceship, Inc., 1 years, 4 months old
PASS
kepalabergetar3k.cfd — via Spaceship, Inc., 1 years, 4 months old
Info::
Domain registered until May 11, 2027 (8 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: Spaceship, Inc.
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

242 days

May 11, 2027

SSL certificate

No certificate data

Domain age

1 years, 4 months

Registered May 11, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a06:98c1:3121::

Registrar

Spaceship, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain 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 Spaceship, Inc.
Created May 11, 2025 (1 years, 4 months ago)
Expires May 11, 2027 (8 months)
Last Updated June 12, 2026
Name Servers demi.ns.cloudflare.com, frank.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2a06:98c1:3121::
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 15 ms TCP Connect 2 ms TLS Handshake 0 ms Server Processing 18 ms Content Transfer 0 ms
A+
Health Check Endpoint
Health endpoint at http://kepalabergetar3k.cfd/healthz (HTTP 200)
PASS
Health endpoint at http://kepalabergetar3k.cfd/healthz (HTTP 200)
Info::
Public health endpoint at http://kepalabergetar3k.cfd/healthz
Got: http://kepalabergetar3k.cfd/healthz
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback