Skip to content
https://diva-portal.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
2
REVIEW
4
PASS
3
INFO
0
Probed from Singapore, Singapore
302 Found
Checks
9
3 PASS 4 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 1992 ms total
FIX
2 redirect(s), 1992 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://diva-portal.org
Warning::
Redirect overhead: 1992 ms total
Got: 1992 ms

https://diva-portal.org

830 ms · HTTP/1.1

302

https://www.diva-portal.org/smash/

652 ms · HTTP/1.1

302

https://www.diva-portal.org/smash/search...

510 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://diva-portal.org302830 msHTTP/1.1Apache/2.4.62 (Debian)
2https://www.diva-portal.org/smash/302652 msHTTP/1.1WildFly/11
3https://www.diva-portal.org/smash/search...200510 msHTTP/1.1WildFly/11

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

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

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
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 302 Expected: 301 redirect to HTTPS

www / non-www

302https://www.diva-portal.org/
200https://diva-portal.org/

Preferred variant: non-www

HTTP → HTTPS

302http://diva-portal.org/ → http://www.diva-portal.org/smash/

HTTP version does not redirect to HTTPS

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

Connection waterfall

DNS Lookup 185 ms TCP Connect 208 ms TLS Handshake 216 ms Server Processing 210 ms Content Transfer 0 ms
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, 190 ms lookup
PASS
1 A records, 190 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 130.238.7.114
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: dns1.uu.se, dns2.uu.se, dns3.uu.se
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
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: 190 ms
Got: 190 ms
A130.238.7.114
AAAA—
CNAME—
NSdns1.uu.se, dns2.uu.se, dns3.uu.se
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 190 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.

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+
Crawlability
robots.txt present, sitemap with 185 URLs
PASS
robots.txt present, sitemap with 185 URLs
Info::
robots.txt is present
Got: 621 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 185 entries
Info::
Sitemap index with 185 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 621 B Sitemaps referenced 1 User-agents Scrapy, Riddler, SemanticScholarBot, Mail.Ru, coccoc, SemrushBot, *, Baiduspider, Yandex, AhrefsBot, SemrushBot-SA Blocking No — crawling allowed
User-agent: Baiduspider
Disallow: /
User-agent: Yandex
Disallow: /
User-agent: Mail.Ru
Disallow: /
User-agent: AhrefsBot
Disallow: /
User-agent: coccoc
Disallow: /
User-agent: SemrushBot
Disallow: /
User-agent: SemrushBot-SA
Disallow: /
User-agent: Scrapy
Disallow: /
User-agent: Riddler
Disallow: /

User-agent: SemanticScholarBot
Crawl-delay: 30
Allow: /

User-agent: *
Crawl-delay: 10
Disallow: /webstats/
Disallow: /dream/
Disallow: /login/
Disallow: /smash/statistics.jsf
Disallow: /smash/builder.jsf
Disallow: /smash/references
Disallow: /smash/resultList.jsf

Sitemap: http://www.diva-portal.org/sitemap-index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 185 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
diva-portal.org — via Ascio Technologies, Inc. Danmark - Filial af Ascio technologies, Inc. USA, 22 years, 6 months old, hosted on UUNET, SE
PASS
diva-portal.org — via Ascio Technologies, Inc. Danmark - Filial af Ascio technologies, Inc. USA, 22 years, 6 months old, hosted on UUNET, SE
Info::
Domain registered until Feb 4, 2027 (9 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: Ascio Technologies, Inc. Danmark - Filial af Ascio technologies, Inc. USA
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: UUNET, SE
Got: AS2834
Domain expiry

234 days

February 4, 2027

SSL certificate

76 days

Issued by Let's Encrypt

Domain age

22 years, 6 months

Registered February 4, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

UUNET, SE

ASN AS2834

130.238.7.114

Registrar

Ascio Technologies, Inc. Danmark - Filial af Ascio technologies, Inc. USA

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL 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 Ascio Technologies, Inc. Danmark - Filial af Ascio technologies, Inc. USA
Created February 4, 2004 (22 years, 6 months ago)
Expires February 4, 2027 (9 months)
Last Updated January 7, 2026
Name Servers dns.uu.se, dns1.uu.se, dns2.uu.se
DNSSEC Not enabled
Hosting
IP Address 130.238.7.114
ASN AS2834 (UUNET, SE)
Provider UUNET, SE
Data source: rdap (1.1s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback