Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain1 redirect(s), 1931 ms totalREVIEW
https://au.dk
838 ms · HTTP/1.1
https://www.au.dk/
1093 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://au.dk | 302 | 838 ms | HTTP/1.1 | |
| 2 | https://www.au.dk/ | 200 | 1093 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
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
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
CURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
BHTTP Probe TimingTotal 856 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations67 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
ADNS Records1 A records, 203 ms lookupPASS
| A | 185.45.20.48 |
| AAAA | — |
| CNAME | — |
| NS | ns3.au.dk, ns4.au.dk |
| MX | 10 au-dk.m-v1.mx.microsoft |
| TXT | HARICA-6Qf59HXTkKhLQAnEiXF SPF v=spf1 include:spf.au.dk -all +iP7dH9sQ7U6Bizb5xnlnP1XHsguI/P3TfT9D3uaDJU= eUWetivz3T6kSv0rVsZctuxW608nPMLSD2OOrysnUJY= feM2adQcQxv1whDnMIPyaXUfBUntVwKt0RByr6toeoU= v=msv1 t=ACEC4DAA-8F71-4B7A-BF61-05179ED7BA3D facebook-domain-verification=j5idhj3z2q5z0g278fbvz0r9a6514t facebook-domain-verification=utyroagwj8u8kxmw2ic2lppqoyl7ci _globalsign-domain-verification=_s8DS-NJexcgiiwmad7BTd5cb8ZNjQB8ud5pKppY8K +Fnrpf/C6TrPbElr0B4fQGjNEYRd4T/ytAhMD8ykt/moByOIDbK0I6RMUBqJ0TVjSMNzyiD51EX7Ujot... ppO+5CUA3y6OgCCZsRDPvU6O8Xixg5zXQ6Grj78SgEA/H44nZaQ+ZuSjSSQEPHw/JhIRBvtMLwOkhWl0... cisco-ci-domain-verification=32d3e8846a2f05d750cd8b256efb1007d1dbe8b5cd6332d1776... |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
ACrawlabilityno robots.txt, sitemap with 15 URLsPASS
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.
Learn more ▾ ▴
A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.
Source: robotstxt.org
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
- https://www.au.dk/sitemap.xml?sitemap=pa...
- https://www.au.dk/sitemap.xml?sitemap=pu...
- https://www.au.dk/sitemap.xml?page=1&sit...
- https://www.au.dk/sitemap.xml?page=2&sit...
- https://www.au.dk/sitemap.xml?page=3&sit...
- https://www.au.dk/sitemap.xml?page=4&sit...
- https://www.au.dk/sitemap.xml?page=5&sit...
- https://www.au.dk/sitemap.xml?page=6&sit...
- https://www.au.dk/sitemap.xml?page=7&sit...
- https://www.au.dk/sitemap.xml?page=8&sit...
- https://www.au.dk/sitemap.xml?page=9&sit...
- https://www.au.dk/sitemap.xml?page=10&si...
- https://www.au.dk/sitemap.xml?page=11&si...
- https://www.au.dk/sitemap.xml?page=12&si...
- https://www.au.dk/sitemap.xml?page=13&si...
A+Domain Intelligenceau.dk — 30 years, 7 months old, hosted on AU-ASN, DKPASS
288 days
March 31, 2027
67 days
Issued by Let's Encrypt
30 years, 7 months
Registered February 2, 1996
Status unknown
Protects against DNS spoofing
AU-ASN, DK
ASN AS62138
185.45.20.48
Registrar unknown
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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