Skip to content
https://birminghammail.co.uk

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 Sao Paulo, Brazil
301 Moved Permanently
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.

B
Redirect Chain
1 redirect(s), 1498 ms total
REVIEW
1 redirect(s), 1498 ms total
Info::
Single redirect
Got: https://birminghammail.co.uk → https://www.birminghammail.co.uk/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1498 ms total
Got: 1498 ms

https://birminghammail.co.uk

818 ms · HTTP/1.1

301

https://www.birminghammail.co.uk/

680 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://birminghammail.co.uk301818 msHTTP/1.1Apache
2https://www.birminghammail.co.uk/200680 msHTTP/1.1CloudFront

See the visual redirect chain in the HTTP Probe tab →

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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.birminghammail.co.uk/
200https://birminghammail.co.uk/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://birminghammail.co.uk/ https://www.birminghammail.co.uk/

Consistent

B
TLS Certificate Expiry & Recommendations
118 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

118
days left
0d 30d 60d 90d+

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 Records
2 A records, 11 ms lookup
PASS
2 A records, 11 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 52.209.217.81, 52.48.6.184
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1402.awsdns-47.org, ns-1669.awsdns-16.co.uk, ns-464.awsdns-58.com, ns-570.awsdns-07.net
Info::
5 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: 11 ms
Got: 11 ms
A52.209.217.81, 52.48.6.184
AAAA
CNAME
NSns-1402.awsdns-47.org, ns-1669.awsdns-16.co.uk, ns-464.awsdns-58.com, ns-570.awsdns-07.net
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
facebook-domain-verification=6041op2qer1rcv72fs3zsvd41vd6ad
google-site-verification=Bd-y5kiiXY1anTYgZvNyhMraP3Vrxd5qwhCpKJWFr0w
google-site-verification=CQVJrhr2DtccoBfZMrLqylZHAVz86iehF5BMv2BKIEI
google-site-verification=E9XYgbqWgtMeZfY4RE01gdWI4xHYqjVa1cCpBtP2kww
google-site-verification=LjEEq4y6Rng4ZWGJLaQYTGZZ-jqlL44gkqiVnktoKo8
google-site-verification=PT5_jfwZ8r8ldvS6n6jvMHwkRGJr1B9UPvD0YLjB_V0
google-site-verification=mk9j0cjC0dBQK507Z5s7yEhdmImcEKfNj6hwBL18_b4
google-site-verification=vvzLBcGgr2SElnwZXO3BZgG__7A1i7ioNrNVVzTjFNQ
tollbit-domain-verification=c4bdb13d5575bf7c477538901f49e99e30375b383a80305d6af3...
SPF v=spf1 include:_spf.google.com include:amazonses.com ~all
CAALookup not available with standard resolver
Resolved in 11 ms

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+
Crawlability
robots.txt present, sitemap with 306 URLs
PASS
robots.txt present, sitemap with 306 URLs
Info::
robots.txt is present
Got: 939 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 306 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 939 B Sitemaps referenced 2 User-agents YouBot, Claude-Web, grapeshot, ozone, Meta-ExternalAgent, Perplexity-ai, ClaudeBot, GPTBot, Applebot-Extended, PerplexityBot, anthropic-ai, AmazonAdBot, *, AhrefsBot, OAI-SearchBot, semetrical, CCBot Blocking No — crawling allowed
Sitemap: https://www.birminghammail.co.uk/map_news.xml
Sitemap: https://www.birminghammail.co.uk/sitemaps/sitemap_index.xml
User-agent: *
Disallow: /topics/*
Disallow: /topics
Disallow: /*token=*
Disallow: /search/
Disallow: /comm-part-test/
Disallow: /*service=ajax
Disallow: /*.ece
Disallow: /5293/
Disallow: /exclusive-offers/
Crawl-delay: 10.0

User-agent: semetrical
Disallow: /

User-agent: AhrefsBot 
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: Perplexity-ai
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: YouBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: grapeshot
Crawl-delay: 0

User-agent: AmazonAdBot
Crawl-delay: 0

User-agent: ozone
Crawl-delay: 0

User-agent: Meta-ExternalAgent
Disallow: /
A+
Domain Intelligence
birminghammail.co.uk — via CSC Corporate Domains, Inc, 20 years, 9 months old, hosted on AWS
PASS
birminghammail.co.uk — via CSC Corporate Domains, Inc, 20 years, 9 months old, hosted on AWS
Info::
Domain registered until Oct 15, 2026 (5 months remaining)
Info::
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.
Info::
Registrar: CSC Corporate 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

121 days

October 15, 2026

SSL certificate

118 days

Issued by Amazon

Domain age

20 years, 9 months

Registered October 15, 2005

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

52.48.6.184

Registrar

CSC Corporate Domains, Inc

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 CSC Corporate Domains, Inc
Created October 15, 2005 (20 years, 9 months ago)
Expires October 15, 2026 (5 months)
Last Updated October 11, 2025
Name Servers ns-1402.awsdns-47.org., ns-1669.awsdns-16.co.uk., ns-464.awsdns-58.com., ns-570.awsdns-07.net.
DNSSEC Not enabled
Hosting
IP Address 52.48.6.184
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (1.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 800 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
12 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
196 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
395 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
800 ms
Total Time Total request time from DNS lookup through full response.
800 ms

Connection waterfall

DNS Lookup 12 ms TCP Connect 196 ms TLS Handshake 395 ms Server Processing 197 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