Skip to content
https://aau.dk

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
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.

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
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.aau.dk/
200https://aau.dk/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://aau.dk/ → https://www.aau.dk/

Consistent

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

Certificate validity

76
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
A+
DNS Records
1 A records, 11 ms lookup
PASS
1 A records, 11 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 20.224.132.89
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: ns0243.secondary.cloudflare.com, ns0122.secondary.cloudflare.com
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 11 ms
Got: 11 ms
A20.224.132.89
AAAA—
CNAME—
NSns0243.secondary.cloudflare.com, ns0122.secondary.cloudflare.com
MX
10 aau-dk.mail.protection.outlook.com
TXT
DomainVerification=QH0BA7VHK3I0A12X6UD47DYDP5C0QB6L96T9M0W6Y0UXV8CQB4C4C33X5MCMU...
HARICA-t5AfFTGr76OE5uIaHnH
MS=ms24336085
adobe-idp-site-verification=377352ae79cbad27a7fa503684623b58becc8c65753a15e4f789...
apple-domain-verification=Oy3oswMDjRrhM1Ql
atlassian-domain-verification=VZsA2T6hFJg72/c1REox7aKjvGy1mYrXDtSL1vCnyXO3G4HQgR...
d365mktkey=14yii8czuyiouy2ojp6fg7b4
d365mktkey=4ruxWRtcS31TzAS0xbPGJuPJBcSwMe5hOBT2y4vXre4x
d365mktkey=b3qAdEtBRECRPGWEnVjQtqFJYl22qMoSuAxxAY2A1rIx
d365mktkey=lx0LJxo3k1FGJOdFWTz9i7ylG3AP5eJkLF3HRDuTCWkx
docusign=a1468f5b-2520-45ec-99f2-e50f27545ca8
facebook-domain-verification=qdtr8jy1ii880wdt9stpeg8ffkaq6m
fp3g9hs2n74g9hkf50i0u938eo
google-site-verification=w89-F2MD6W8pzUnZim0MdMwZAamu0q7s7XiU1p8K9QY
i58tUtFPHd1d7Hdk+0SozdOYXYyUHOREOjrZ77bZFzE0vJc3HlLVdz9FQSQ0KHb9mvf4HjuSUTUU+U2o...
mentimeter-80765762-68ce-40e2-9b18-f31d99c02737
mistral-domain-verification=9b0b768e286a5c404f880353551ac9159e986e06
n0j4liboai56f2k63ol7vc18fd
SPF v=spf1 include:_spfhard.aau.dk include:_spf.varbi.com ip4:89.250.112.0 ip4:192....
CAALookup not available with standard resolver
Resolved in 11 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 566 ms total
PASS
1 redirect(s), 566 ms total
Info::
Single redirect
Got: https://aau.dk → https://www.aau.dk/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 566 ms total
Got: 566 ms

https://aau.dk

239 ms · HTTP/1.1

301

https://www.aau.dk/

327 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://aau.dk301239 msHTTP/1.1nginx/1.29.3
2https://www.aau.dk/200327 msHTTP/1.1nginx/1.29.3

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 1736 URLs
PASS
robots.txt present, sitemap with 1736 URLs
Info::
robots.txt is present
Got: 22 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1736 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 22 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
sitemap.xml 200 OK
Type URL Set URLs 1736 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
aau.dk — 28 years, 10 months old, hosted on Microsoft Azure
PASS
aau.dk — 28 years, 10 months old, hosted on Microsoft Azure
Info::
Domain registered until Dec 31, 2028 (2 years, 8 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.
Info::
Hosting: Microsoft Azure
Got: AS8075
Domain expiry

929 days

December 31, 2028

SSL certificate

76 days

Issued by Let's Encrypt

Domain age

28 years, 10 months

Registered October 31, 1997

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

20.224.132.89

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 October 31, 1997 (28 years, 10 months ago)
Expires December 31, 2028 (2 years, 8 months)
Name Servers ns0122.secondary.cloudflare.com, ns0243.secondary.cloudflare.com
Hosting
IP Address 20.224.132.89
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: whois (0.4s)

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

Connection waterfall

DNS Lookup 4 ms TCP Connect 78 ms TLS Handshake 80 ms Server Processing 78 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback