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.
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
BTLS Certificate Expiry & Recommendations46 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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 Records1 A records, 28 ms lookupPASS
| A | 165.22.4.137 |
| AAAA | — |
| CNAME | — |
| NS | ns3.digitalocean.com, ns1.digitalocean.com, ns2.digitalocean.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com |
| TXT | protonmail-verification=c06c254af241efeb838afeadb6728d3c2a4eb73d mailerlite-domain-verification=67e3b4e4bf9ce3d0b4e188d292dd1932602b69db ahrefs-site-verification_9ca56189252c470afa3c05215b4a6fd706546275b157c2ee02a21b3... google-site-verification=xDObohExH6_RKAKqNXEytgRqeIS8Rq4uH46pQeDhn0Q mailerlite-domain-verification=d69304e4175464ff9c5fd33455cb3f6a777988cb dropbox-domain-verification=3caithxkobez SPF v=spf1 a mx include:_spf.mlsend.com include:_spf.google.com ~all google-site-verification=yKyE6SxpfHwyABZkp6W2OxBH9L0Lyso5VFi0dixTIz8 asv=289f1145efb7dd6acd348da3755183f2 facebook-domain-verification=p2w87rvximachb1r2ob9nrtann8qty _globalsign-domain-verification=ncHr8tTugqw45BXbT7AehwRBL3QVoa971i3ngM2Jvk |
| 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.
ARedirect Chain1 redirect(s), 634 ms totalPASS
https://interaction-design.org
442 ms · HTTP/1.1
https://ixdf.org/
192 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://interaction-design.org | 301 | 442 ms | HTTP/1.1 | nginx |
| 2 | https://ixdf.org/ | 200 | 192 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
ACrawlabilityno robots.txt, sitemap with 12 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://ixdf.org/sitemap/pages.xml
- https://ixdf.org/sitemap/courses.xml
- https://ixdf.org/sitemap/career-programs...
- https://ixdf.org/sitemap/masterclasses.x...
- https://ixdf.org/sitemap/articles.xml
- https://ixdf.org/sitemap/books.xml
- https://ixdf.org/sitemap/book-chapters.x...
- https://ixdf.org/sitemap/topic-definitio...
- https://ixdf.org/sitemap/local-groups.xm...
- https://ixdf.org/sitemap/authors.xml
- https://ixdf.org/sitemap/members.xml
- https://ixdf.org/sitemap/job-postings.xm...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceinteraction-design.org — via pair Networks, Inc. d/b/a pair Domains, 26 years, 3 months old, hosted on DigitalOceanPASS
2889 days
May 13, 2034
46 days
Issued by Let's Encrypt
26 years, 3 months
Registered May 13, 2000
Not enabled
Protects against DNS spoofing
DigitalOcean
ASN AS14061
165.22.4.137
pair Networks, Inc. d/b/a pair Domains
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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