Skip to content
https://www.adamnordling.se

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
8 PASS 9 REVIEW
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/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 188.114.96.2: lookup 188.114.96.2: 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 188.114.97.2: lookup 188.114.97.2: 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 2a06:98c1:3121::2: lookup 2a06:98c1:3121::2: 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 2a06:98c1:3120::2: lookup 2a06:98c1:3120::2: 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
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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.adamnordling.se/
200https://adamnordling.se/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.adamnordling.se/ → https://adamnordling.se/

Consistent

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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 & Delivery
Document and assets on Cloudflare
REVIEW
Document and assets on Cloudflare
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a3f8ac46aad645f1-CDG
Info::
Assets on Cloudflare: adamnordling.se (assets: 4), cache HIT
Got: cf-ray: a3f8ad251b0114c6-CDG
Document served via CDN: Cloudflare
Provider Cloudflare Evidence cf-ray: a3f8ac46aad645f1-CDG

Asset hosts on a CDN

  • adamnordling.se — Cloudflare · assets: 4 · Cache Status: HIT
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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A
DNS Records
2 A records, 56 ms lookup
PASS
2 A records, 56 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 188.114.96.2, 188.114.97.2
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3121::2, 2a06:98c1:3120::2
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: 56 ms
Got: 56 ms
A188.114.96.2, 188.114.97.2
AAAA2a06:98c1:3121::2, 2a06:98c1:3120::2
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 56 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 21ms across 3 resolvers (spread 19ms)
PASS
Mean 21ms across 3 resolvers (spread 19ms)
Info::
Quad9: 9ms
Got: 9ms via 9.9.9.9:53
Info::
Cloudflare: 26ms
Got: 26ms via 1.1.1.1:53
Info::
Google: 28ms
Got: 28ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 118 ms total
PASS
1 redirect(s), 118 ms total
Info::
Single redirect
Got: https://www.adamnordling.se → https://adamnordling.se/ (301)
Info::
WWW normalization redirect

https://www.adamnordling.se

33 ms · HTTP/1.1

301

https://adamnordling.se/

85 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.adamnordling.se30133 msHTTP/1.1cloudflare
2https://adamnordling.se/20085 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:3121::2, 2a06:98c1:3120::2
Got: 16 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:3121::2, 2a06:98c1:3120::2 Connection Reachable (16 ms)
A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 68 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 68 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /

Sitemap: https://adamnordling.se/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 1 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
adamnordling.se — via Loopia AB, 4 days old
PASS
adamnordling.se — via Loopia AB, 4 days old
Info::
Domain registered until Sep 19, 2027 (1 years remaining)
Info::
Domain is only 4 days old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Sep 19, 2026
Info::
Registrar: Loopia AB
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

360 days

September 19, 2027

SSL certificate

86 days

Issued by Google Trust Services

Domain age

4 days

Registered September 19, 2026

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a06:98c1:3120::2

Registrar

Loopia AB

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Loopia AB
Created September 19, 2026 (4 days ago)
Expires September 19, 2027 (1 years)
Last Updated September 19, 2026
Name Servers leonard.ns.cloudflare.com, arely.ns.cloudflare.com
Registrant (not shown)
Hosting
IP Address 2a06:98c1:3120::2
Data source: whois (0.6s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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 126 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
67 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.
24 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
127 ms
Total Time Total request time from DNS lookup through full response.
127 ms

Connection waterfall

DNS Lookup 67 ms TCP Connect 17 ms TLS Handshake 24 ms Server Processing 19 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