Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSFIX
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
HTTP version does not redirect to HTTPS
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 & Recommendations249 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, 5 ms lookupPASS
| A | 184.106.62.251 |
| AAAA | — |
| CNAME | — |
| NS | pdns03.domaincontrol.com, pdns04.domaincontrol.com |
| MX | 0 d332647b.ess.barracudanetworks.com 0 d332647a.ess.barracudanetworks.com 10 arrl-org.mail.protection.outlook.com |
| TXT | SPF v=spf1 mx a ip4:104.207.196.0/27 ip4:184.106.62.251 ip4:104.130.222.72 ip4:23.25... google-site-verification=wr3UIcZuLM075hZ_IDYVrmSi5hm48n_jfBo9EOxnipQ s75KlRvy2ICfMkRrFGXzjSNGbRJLVsjeMVtbm9UXImSDp3pWSnoZmaSJpn90yCXlDzZgeWdBZx9/YX/d... MS=ms86081500 mrq57g1cf333vme2hh2bsbkirr google-site-verification=eYvVCCer_TcWz5PdKsbQEY9XV7ewks4Rr6-mA710lj4 |
| 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.
A+Redirect Chain0 redirect(s), 93 ms totalPASS
https://arrl.org
93 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://arrl.org | 302 | 93 ms | HTTP/1.1 | Apache |
If permanent, use 301 instead.
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
A+Crawlabilityrobots.txt present, sitemap with 1133 URLsPASS
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Disallow: /files/file/protected
Disallow: /attachments/download
Disallow: /admin
Disallow: /ad_upload
Disallow: /advertising-upload.php
Disallow: /vec_upload
Disallow: /vec-upload.php
Disallow: /results-database
Disallow: /webroot/index.php/Pages/view/
Disallow: /volunteer-monitor-resources
Crawl-delay: 5
A+Domain Intelligencearrl.org — via GoDaddy.com, LLC, 34 years, 5 months old, hosted on RackspacePASS
1437 days
May 21, 2030
249 days
Issued by GoDaddy.com, Inc.
34 years, 5 months
Registered May 20, 1992
Not enabled
Protects against DNS spoofing
Rackspace
ASN AS19994
184.106.62.251
GoDaddy.com, LLC
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