Infrastructure - https://ala.org BeaverCheck Audit

B

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

REVIEW

www/non-www, trailing slash, HTTP→HTTPS

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.ala.org/

200https://ala.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ala.org/ → https://www.ala.org/

Consistent

B

TLS Certificate Expiry & Recommendations

87 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

87

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, 9 ms lookup

PASS

1 A records, 9 ms lookup

Resolves to 1 IPv4 address(es)

Got: 23.185.0.1

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 2 IPv6 (AAAA) record(s)

Got: 2620:12a:8001::1, 2620:12a:8000::1

4 nameserver(s) configured

Got: ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info

1 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 9 ms

Got: 9 ms

A	23.185.0.1
AAAA	2620:12a:8001::1, 2620:12a:8000::1
CNAME	—
NS	ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info
MX	0 ala-org.mail.protection.outlook.com
TXT	SPF v=spf1 include:a675yby0um.powerspf.com ?all cdbw991thlg2j2b39fh2rbw88sxkbgry google-site-verification=hCSyQ4LSa2VWKuWUd846wfkgU15Gg2j0qo2vzU5aIoA google-site-verification=4vbSg0s2_y49n0m-r6nXSwLVhT2OGkF--o1OwguJ7e8 r4jk2zc401xkt3dt8csxhsdh0m1129xt MS=ms97633839 google-site-verification=3TVm4bZ4CaowKigBbjCtHydUt8iG5MHHRH-KwTUgtbE google-site-verification=eRCqgUUqK50CDCflQhkjo-F9cEU-Thsz1PhxOhdDKSw asv=3df61a2e4f9b9ec8cc98f3b4ba364654
CAA	Lookup not available with standard resolver

Resolved in 9 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.

A

Redirect Chain

1 redirect(s), 53 ms total

PASS

1 redirect(s), 53 ms total

Single redirect

Got: https://ala.org → https://www.ala.org/ (301)

WWW normalization redirect

https://ala.org

24 ms · HTTP/1.1

301

https://www.ala.org/

30 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://ala.org	301	24 ms	HTTP/1.1	Pantheon
2	https://www.ala.org/	200	30 ms	HTTP/1.1	nginx

See the visual redirect chain in the HTTP Probe tab →

A+

IPv6 Readiness

IPv6 reachable (1 ms)

PASS

IPv6 reachable (1 ms)

IPv6 is configured and reachable at 2620:12a:8001::1, 2620:12a:8000::1

Got: 1 ms connect

IPv6 Ready

AAAA Records 2620:12a:8001::1, 2620:12a:8000::1 Connection Reachable (1 ms)

A+

Crawlability

robots.txt present, sitemap with 32 URLs

PASS

robots.txt present, sitemap with 32 URLs

robots.txt is present

Got: 4819 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 32 entries

Sitemap index with 32 child sitemaps

robots.txt does not reference a sitemap

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK

Size 4819 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed

#

# robots.txt

#

# This file is to prevent the crawling and indexing of certain parts

# of your site by web crawlers and spiders run by sites like Yahoo!

# and Google. By telling these "robots" where not to go on your site,

# you save bandwidth and server resources.

#

# This file will be ignored unless it is at the root of your host:

# Used:    http://example.com/robots.txt

# Ignored: http://example.com/site/robots.txt

#

# For more information about the robots.txt standard, see:

# http://www.robotstxt.org/robotstxt.html


User-agent: *

Crawl-delay: 10
# CSS, JS, Images

Allow: /core/*.css$

Allow: /core/*.css?

Allow: /core/*.js$

Allow: /core/*.js?

Allow: /core/*.gif

Allow: /core/*.jpg

Allow: /core/*.jpeg

Allow: /core/*.png

Allow: /core/*.svg

Allow: /profiles/*.css$

Allow: /profiles/*.css?

Allow: /profiles/*.js$

Allow: /profiles/*.js?

Allow: /profiles/*.gif

Allow: /profiles/*.jpg

Allow: /profiles/*.jpeg

Allow: /profiles/*.png

Allow: /profiles/*.svg

# Directories

Disallow: /core/

Disallow: /profiles/

Disallow: /system/files/media-private-documents/

# Files

Disallow: /README.md

Disallow: /composer/Metapackage/README.txt

Disallow: /composer/Plugin/ProjectMessage/README.md

Disallow: /composer/Plugin/Scaffold/README.md

Disallow: /composer/Plugin/VendorHardening/README.txt

Disallow: /composer/Template/README.txt

Disallow: /modules/README.txt

Disallow: /sites/README.txt

Disallow: /themes/README.txt

Disallow: /web.config

# Paths (clean URLs)

Disallow: /admin/

Disallow: /comment/reply/

Disallow: /filter/tips

Disallow: /node/add/

Disallow: /search/

Disallow: /user/register

Disallow: /user/password

Disallow: /user/login

Disallow: /user/logout

Disallow: /media/oembed

Disallow: /*/media/oembed

# Paths (no clean URLs)

Disallow: /index.php/admin/

Disallow: /index.php/comment/reply/

Disallow: /index.php/filter/tips

Disallow: /index.php/node/add/

Disallow: /index.php/search/

Disallow: /index.php/user/password

Disallow: /index.php/user/register

Disallow: /index.php/user/login

Disallow: /index.php/user/logout

Disallow: /index.php/media/oembed

Disallow: /index.php/*/media/oembed
Allow: /core/2024-interest-group-week
Allow: /core/about
Allow: /core/about/*
Allow: /core/advocacy-issues
Allow: /core/advocacy/*
Allow: /core/alaiida-library-interior-design-award
Allow: /core/assembling-your-consultant-tool-kit-what-you-need-know-become-successful-consultant
Allow: /core/awards-and-scholarships/*
Allow: /core/awards-scholarships
Allow: /core/awards-scholarships/*
Allow: /core/benefits-membership
Allow: /core/board-directors
Allow: /core/ce/*
Allow: /core/clone-benefits-membership
Allow: /core/clone-clone-find-committee-volunteer-opportunities-v2
Allow: /core/clone-core-ala-annual-2025
Allow: /core/clone-core-ala-annual-2025-0
Allow: /core/clone-core-courses
Allow: /core/clone-find-committee-volunteer-opportunities
Allow: /core/clone-find-committee-volunteer-opportunities-0
Allow: /core/clone-fundamentals-institutional-repositories
Allow: /core/committees/*
Allow: /core/conferences
Allow: /core/conferences/*
Allow: /core/consortial-borrowing-committee-joint-committee-rusa
Allow: /core/contact
Allow: /core/continuing-education
Allow: /core/continuing-education/*
Allow: /core/core-ala-annual-2023
Allow: /core/core-ala-annual-2025
Allow: /core/core-ala-annual-2025-copy-2
Allow: /core/core-ala-annual-2025/*
Allow: /core/core-ala-annual-2026
Allow: /core/core-at-ala-annual
Allow: /core/core-calendar
Allow: /core/core-chicago-area-public-library-tours
Allow: /core/core-competencies
Allow: /core/core-innovative-learning-spaces-tour-innovative-chicago-area-academic-institutions
Allow: /core/core-libguides
Allow: /core/core-sandbox
Allow: /core/core-sponsors
Allow: /core/e-forums
Allow: /core/explore-core
Allow: /core/faq-presenting-core-webinar
Allow: /core/governance/*
Allow: /core/interest-group-week
Allow: /core/introduction-library-assessment
Allow: /core/jobs/*
Allow: /core/koha-sandbox-request
Allow: /core/leadership-orientation-guide
Allow: /core/llama-alaaia-library-building-awards
Allow: /core/member-center
Allow: /core/member-center/*
Allow: /core/merchandise-mart-furniture-showrooms-and-factory-tour
Allow: /core/migration-madness-and-how-get-through-it
Allow: /core/node/*
Allow: /core/preservation-action
Allow: /core/press-releases/*
Allow: /core/program-proposal
Allow: /core/publication-policies
Allow: /core/publications
Allow: /core/publications/*
Allow: /core/publish
Allow: /core/resources-tools
Allow: /core/resources-tools/*
Allow: /core/sandbox-access-request
Allow: /core/search-core-committees
Allow: /core/sections/*
Allow: /core/stay-current
Allow: /core/stay-current/*
Allow: /core/test-2
Allow: /core/unlocking-power-rda-joint-workshop-nardac-and-pcc-sct-rda-training-task-group

sitemap.xml 200 OK

Type Sitemap Index URLs 32 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

ala.org — via Network Solutions, LLC, 32 years, 8 months old

PASS

ala.org — via Network Solutions, LLC, 32 years, 8 months old

Domain registered until Jan 19, 2027 (9 months remaining)

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.

Registrar: Network Solutions, LLC

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

184 days

January 19, 2027

SSL certificate

87 days

Issued by Let's Encrypt

Domain age

32 years, 8 months

Registered January 18, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2620:12a:8001::1

Registrar

Network Solutions, LLC

Unlocked 4 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 Network Solutions, LLC

Created January 18, 1994 (32 years, 8 months ago)

Expires January 19, 2027 (9 months)

Last Updated February 3, 2025

Name Servers ns3-05.azure-dns.org, ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns4-05.azure-dns.info

DNSSEC Not enabled

Hosting

IP Address 2620:12a:8001::1

Data source: rdap (0.3s)

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

A+

HTTP Probe Timing

Total 30 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

8 ms

TCP Connect

2 ms

TLS Handshake

8 ms

Time to First Byte

30 ms

Total Time

31 ms

Connection waterfall

DNS Lookup 8 ms TCP Connect 2 ms TLS Handshake 8 ms Server Processing 13 ms Content Transfer 0 ms

A+

CDN & Delivery

Fastly (HIT)

PASS

Fastly (HIT)

Site is served via Fastly CDN

Got: x-served-by: cache-gru-sbsp2090080-GRU

CDN cache status: HIT

CDN Detected: Fastly

Provider Fastly Cache Status HIT Evidence x-served-by: cache-gru-sbsp2090080-GRU