Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/4 IPs match cert SANREVIEW
BCrawlabilityrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
User-agent: *
Allow: /
Disallow: /ui/
Disallow: /*?access=
Disallow: /*&access=
Disallow: /*?areas=
Disallow: /*&areas=
Disallow: /*?choice=
Disallow: /*&choice=
Disallow: /*?concept=
Disallow: /*&concept=
Disallow: /*?cost=
Disallow: /*&cost=
Disallow: /*?fee=
Disallow: /*&fee=
Disallow: /*?properties=
Disallow: /*&properties=
Disallow: /*?query=
Disallow: /*&query=
Disallow: /*?rent=
Disallow: /*&rent=
Disallow: /*?rooms=
Disallow: /*&rooms=
Disallow: /*?sort=
Disallow: /*&sort=
Disallow: /*?tab=
Disallow: /*&tab=
Disallow: /*?tenure=
Disallow: /*&tenure=
Disallow: /*?type=
Disallow: /*&type=
Disallow: /*?types=
Disallow: /*&types=
Disallow: /*?view=
Disallow: /*&view=
Sitemap: https://www.riksbyggen.se/sitemap.xml
BTLS Certificate Expiry & Recommendations44 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Add includeSubDomains to the HSTS directive
- 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
BOperational Status PageNo status page link detectedREVIEW
ADNS Records2 A records, 38 ms lookupPASS
| A | 104.18.40.67, 172.64.147.189 |
| AAAA | 2606:4700:4409::6812:2843, 2a06:98c1:310d::ac40:93bd |
| CNAME | www.riksbyggen.se.dxcloud.episerver.net |
| NS | austin.ns.cloudflare.com, desi.ns.cloudflare.com |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
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 TakeoverNo subdomain takeover risk detectedPASS
AMulti-Resolver DNS SpeedMean 56ms across 3 resolvers (spread 83ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://www.riksbyggen.se
186 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.riksbyggen.se | 200 | 186 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (16 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
ADomain Intelligenceriksbyggen.se — via Abion AB, 31 years oldPASS
52 days
December 31, 2026
44 days
Issued by Google Trust Services
31 years
Registered April 2, 1996
Status unknown
Protects against DNS spoofing
Unknown
2a00:1c50:94::2
Abion AB
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Consider enabling auto-renewal to prevent accidental expiration.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
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