Skip to content
https://fortryd.dccenergi.dk

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
5
PASS
11
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
11 PASS 5 REVIEW 1 FIX
D
Crawlability
Action
robots.txt present, sitemap with 0 URLs
FIX
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 27 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: 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

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 27 B Sitemaps referenced 0 User-agents * Blocking Yes — all crawlers blocked
User-Agent: *
Disallow: /
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
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/6 IPs match cert SAN
REVIEW
0/6 IPs match cert SAN
Info::
PTR lookup failed for 104.26.0.32: lookup 104.26.0.32: 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 104.26.1.32: lookup 104.26.1.32: 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 172.67.68.175: lookup 172.67.68.175: 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 2606:4700:20::681a:20: lookup 2606:4700:20::681a:20: 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 2606:4700:20::ac43:44af: lookup 2606:4700:20::ac43:44af: 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 2606:4700:20::681a:120: lookup 2606:4700:20::681a:120: 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 — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • 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.
A
DNS Records
3 A records, 63 ms lookup
PASS
3 A records, 63 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.0.32, 104.26.1.32, 172.67.68.175
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::681a:20, 2606:4700:20::ac43:44af, 2606:4700:20::681a:120
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: 63 ms
Got: 63 ms
A104.26.0.32, 104.26.1.32, 172.67.68.175
AAAA2606:4700:20::681a:20, 2606:4700:20::ac43:44af, 2606:4700:20::681a:120
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 63 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 18ms across 3 resolvers (spread 32ms)
PASS
Mean 18ms across 3 resolvers (spread 32ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 33ms
Got: 33ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://fortryd.dccenergi.dk

https://fortryd.dccenergi.dk

158 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://fortryd.dccenergi.dk200158 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::681a:20, 2606:4700:20::ac43:44af, 2606:4700:20::681a:120
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::681a:20, 2606:4700:20::ac43:44af, 2606:4700:20::681a:120 Connection Reachable (17 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.fortryd.dccenergi.dk/
200https://fortryd.dccenergi.dk/

HTTP → HTTPS

301http://fortryd.dccenergi.dk/ → https://fortryd.dccenergi.dk/

Consistent

A+
Domain Intelligence
dccenergi.dk — 17 years, 4 months old
PASS
dccenergi.dk — 17 years, 4 months old
Info::
Domain registered until Jun 30, 2027 (11 months remaining)
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

350 days

June 30, 2027

SSL certificate

63 days

Issued by Let's Encrypt

Domain age

17 years, 4 months

Registered June 8, 2009

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::681a:120

Registrar

Registrar unknown

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Created June 8, 2009 (17 years, 4 months ago)
Expires June 30, 2027 (11 months)
Name Servers kip.ns.cloudflare.com, mia.ns.cloudflare.com
Hosting
IP Address 2606:4700:20::681a:120
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 282 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
51 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.
25 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
273 ms
Total Time Total request time from DNS lookup through full response.
282 ms

Connection waterfall

DNS Lookup 51 ms TCP Connect 17 ms TLS Handshake 25 ms Server Processing 181 ms Content Transfer 10 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a1b0db80eea4b868-CDG
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a1b0db80eea4b868-CDG
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
A+
Health Check Endpoint
Health endpoint at https://fortryd.dccenergi.dk/api/health (HTTP 200)
PASS
Health endpoint at https://fortryd.dccenergi.dk/api/health (HTTP 200)
Info::
Public health endpoint at https://fortryd.dccenergi.dk/api/health
Got: https://fortryd.dccenergi.dk/api/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback