Infrastructure - https://al-monitor.com 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.al-monitor.com/

200https://al-monitor.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://al-monitor.com/ → https://al-monitor.com/

Consistent

B

TLS Certificate Expiry & Recommendations

60 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

60

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

A+

DNS Records

1 A records, 51 ms lookup

PASS

1 A records, 51 ms lookup

Resolves to 1 IPv4 address(es)

Got: 23.185.0.2

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::2, 2620:12a:8000::2

2 nameserver(s) configured

Got: ian.ns.cloudflare.com, dara.ns.cloudflare.com

5 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: 51 ms

Got: 51 ms

A	23.185.0.2
AAAA	2620:12a:8001::2, 2620:12a:8000::2
CNAME	—
NS	ian.ns.cloudflare.com, dara.ns.cloudflare.com
MX	1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 aspmx3.googlemail.com 10 aspmx2.googlemail.com
TXT	google-site-verification=qx7eEukb1WodpHytFZmvP6D8YNvK29WYwEhGT5vnIig MHudKYb4krjvEo5Vswb0AnZhClcgq2dEoJaKCPCTgF5oLIiN6oHoEYF1+yRs0TK+JfjlHEOQMOlbTXl+... MS=ms65267370 google-site-verification=bYwaDuXnYnlZBiubO8W37x2KcmpyVHAXs_gCWa42shQ firebase=al-monitor-pro-8831b firebase=al-monitor-pro-prod SPF v=spf1 include:_spf.createsend.com include:_spf.google.com ~all google-site-verification=lRxyh_GjwAoWQfB_YJPaBb8RMKZIF6NPQ5Z71xUQHns
CAA	Lookup not available with standard resolver

Resolved in 51 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), 292 ms total

PASS

1 redirect(s), 292 ms total

Single redirect

Got: https://al-monitor.com → https://www.al-monitor.com/ (301)

WWW normalization redirect

https://al-monitor.com

6 ms · HTTP/1.1

301

https://www.al-monitor.com/

286 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://al-monitor.com	301	6 ms	HTTP/1.1	nginx
2	https://www.al-monitor.com/	200	286 ms	HTTP/1.1	nginx

See the visual redirect chain in the HTTP Probe tab →

A+

IPv6 Readiness

IPv6 reachable (0 ms)

PASS

IPv6 reachable (0 ms)

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

Got: 0 ms connect

IPv6 Ready

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

A+

Crawlability

robots.txt present, sitemap with 105 URLs

PASS

robots.txt present, sitemap with 105 URLs

robots.txt is present

Got: 2046 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 105 entries

Sitemap index with 105 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 2046 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: *
# 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/
# 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

Disallow: /search

sitemap.xml 200 OK

Type Sitemap Index URLs 105 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

al-monitor.com — via DreamHost, LLC, 15 years, 3 months old

PASS

al-monitor.com — via DreamHost, LLC, 15 years, 3 months old

Domain registered until Apr 11, 2027 (11 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: DreamHost, 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

301 days

April 11, 2027

SSL certificate

60 days

Issued by Let's Encrypt

Domain age

15 years, 3 months

Registered April 11, 2011

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2620:12a:8001::2

Registrar

DreamHost, LLC

Unlocked 2 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 DreamHost, LLC

Created April 11, 2011 (15 years, 3 months ago)

Expires April 11, 2027 (11 months)

Last Updated March 10, 2026

Name Servers dara.ns.cloudflare.com, ian.ns.cloudflare.com

DNSSEC Not enabled

Hosting

IP Address 2620:12a:8001::2

Data source: rdap (0.1s)

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 55 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

49 ms

TCP Connect

0 ms

TLS Handshake

3 ms

Time to First Byte

55 ms

Total Time

55 ms

Connection waterfall

DNS Lookup 49 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 2 ms Content Transfer 0 ms

A+

CDN & Delivery

Fastly (HIT, HIT)

PASS

Fastly (HIT, HIT)

Site is served via Fastly CDN

Got: x-served-by: cache-chi-kigq8000081-CHI, cache-toj-leto2350075-TOJ

CDN cache status: HIT, HIT

CDN Detected: Fastly

Provider Fastly Cache Status HIT, HIT Evidence x-served-by: cache-chi-kigq8000081-CHI, cache-toj-leto2350075-TOJ