Skip to content
https://brill.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
202 HTTP 202
Checks
9
4 PASS 4 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

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

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 202 Expected: 301 redirect to HTTPS

www / non-www

202https://www.brill.com/
200https://brill.com/

HTTP → HTTPS

202http://brill.com/

HTTP version does not redirect to HTTPS

C
TLS Certificate Expiry & Recommendations
Action
29 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

29
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 29 days remaining
  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 29 ms lookup
PASS
1 A records, 29 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.255.55.51
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns1.kpn.net, ns11.kpn.net
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 29 ms
Got: 29 ms
A34.255.55.51
AAAA
CNAME
NSns1.kpn.net, ns11.kpn.net
MX
10 brill-com.mail.protection.outlook.com
TXT
atlassian-domain-verification=iwRONO9yg8tFsSmntl6YnDtw4xmFhFXacewGetTV58T09v98cm...
0ed1fe018a4d5e2550dbd74813a519a03cc85a0e97
MS=ms38368599
google-site-verification=hI9Rvb1XWwfWX7TVRKbKo3JIok9a7Yy1kh59lfMCGu0
google-site-verification=K3UjqEnjVZ1R7OLjKM8SlZI24U9soa-URXIj5aP1Ya0
SPF v=spf1 include:spf1.brill.com include:spf.protection.outlook.com include:spf.int...
sending_domain1014162=357fa4fc758ac9a08925ec403f833644e3c29ab2fe349447c2bb6b9624...
pardot1014162=bbad90b1e35e4deacb841fae4f1432c113bbb0ef45240bdb248851c9cce7379e
CAALookup not available with standard resolver
Resolved in 29 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://brill.com

https://brill.com

147 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://brill.com202147 msHTTP/1.1awselb/2.0
A+
Domain Intelligence
brill.com — via Tucows Domains Inc., 31 years, 8 months old, hosted on AWS
PASS
brill.com — via Tucows Domains Inc., 31 years, 8 months old, hosted on AWS
Info::
Domain registered until Jan 12, 2027 (8 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Tucows Domains Inc.
Warning::
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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

178 days

January 12, 2027

SSL certificate

29 days

Issued by Sectigo Limited

Domain age

31 years, 8 months

Registered January 13, 1995

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

34.255.55.51

Registrar

Tucows Domains Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Tucows Domains Inc.
Created January 13, 1995 (31 years, 8 months ago)
Expires January 12, 2027 (8 months)
Last Updated December 14, 2025
Name Servers ns1.kpn.net, ns11.kpn.net
DNSSEC Enabled
Hosting
IP Address 34.255.55.51
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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 164 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
22 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
35 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
71 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
164 ms
Total Time Total request time from DNS lookup through full response.
165 ms

Connection waterfall

DNS Lookup 22 ms TCP Connect 35 ms TLS Handshake 71 ms Server Processing 37 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback