Skip to content
https://danbritdirect.dk

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
2
REVIEW
8
PASS
7
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
17
7 PASS 8 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 383ms across 3 resolvers (spread 458ms)
FIX
Mean 383ms across 3 resolvers (spread 458ms)
Info::
Cloudflare: 173ms
Got: 173ms via 1.1.1.1:53
Info::
Quad9: 345ms
Got: 345ms via 9.9.9.9:53
Info::
Google: 631ms
Got: 631ms via 8.8.8.8:53
Info::
High latency spread between resolvers: 458ms (min 173ms / max 631ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
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
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
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 185.20.204.239 does not match any cert SAN: vdom165.net.dk2.zitcom.dk
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 24 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 24 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow:
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
HTTP Probe Timing
Total 1402 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
532 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
172 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
177 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.23 s
Total Time Total request time from DNS lookup through full response.
1.40 s

Connection waterfall

DNS Lookup 532 ms TCP Connect 172 ms TLS Handshake 177 ms Server Processing 348 ms Content Transfer 173 ms
B
TLS Certificate Expiry & Recommendations
89 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
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
1 A records, 747 ms lookup
PASS
1 A records, 747 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.20.204.239
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns1.simply.com, ns2.simply.com, ns3.simply.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (747 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 747 ms
A185.20.204.239
AAAA—
CNAME—
NSns1.simply.com, ns2.simply.com, ns3.simply.com
MX
10 mx.simply.com
TXT
SPF v=spf1 include:spf.simply.com -all
CAALookup not available with standard resolver
Resolved in 747 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+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (ECDSAP256SHA256)
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://danbritdirect.dk

https://danbritdirect.dk

1058 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://danbritdirect.dk2001058 msHTTP/1.1
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)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

301https://www.danbritdirect.dk/
200https://danbritdirect.dk/

Preferred variant: non-www

HTTP → HTTPS

308http://danbritdirect.dk/ → https://danbritdirect.dk

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
danbritdirect.dk — via Simply.com A/S, 9 years, 2 months old, hosted on team-blue-denmark - team.blue Denmark A/S, DK
PASS
danbritdirect.dk — via Simply.com A/S, 9 years, 2 months old, hosted on team-blue-denmark - team.blue Denmark A/S, DK
Info::
Domain registered until May 31, 2027 (11 months remaining)
Info::
Registrar: Simply.com A/S
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: team-blue-denmark - team.blue Denmark A/S, DK
Got: AS48854
Domain expiry

349 days

May 31, 2027

SSL certificate

89 days

Issued by Let's Encrypt

Domain age

9 years, 2 months

Registered May 15, 2017

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

team-blue-denmark - team.blue Denmark A/S, DK

ASN AS48854

185.20.204.239

Registrar

Simply.com A/S

Unlocked 3 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 Simply.com A/S
Created May 15, 2017 (9 years, 2 months ago)
Expires May 31, 2027 (11 months)
Name Servers ns1.simply.com, ns2.simply.com, ns3.simply.com
Hosting
IP Address 185.20.204.239
ASN AS48854 (team-blue-denmark - team.blue Denmark A/S, DK)
Provider team-blue-denmark - team.blue Denmark A/S, DK
Data source: whois (1.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+
Health Check Endpoint
Health endpoint at https://danbritdirect.dk/api/health (HTTP 200)
PASS
Health endpoint at https://danbritdirect.dk/api/health (HTTP 200)
Info::
Public health endpoint at https://danbritdirect.dk/api/health
Got: https://danbritdirect.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