Infrastructure - https://www.lycamobile.co.uk/en/ BeaverCheck Audit

B

DNS Records

2 A records, 33 ms lookup

REVIEW

2 A records, 33 ms lookup

Resolves to 2 IPv4 address(es)

Got: 104.18.6.119, 104.18.7.119

Has 2 IPv6 (AAAA) record(s)

Got: 2606:4700::6812:777, 2606:4700::6812:677

CNAME record at zone apex

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Got: www.lycamobile.co.uk.cdn.cloudflare.net

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution time: 33 ms

Got: 33 ms

A	104.18.6.119, 104.18.7.119
AAAA	2606:4700::6812:777, 2606:4700::6812:677
CNAME	www.lycamobile.co.uk.cdn.cloudflare.net
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 33 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

DNSSEC is not deployed

The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

B

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

No CAA records published

Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

C

Reverse DNS

Action

0/4 IPs match cert SAN

REVIEW

0/4 IPs match cert SAN

PTR lookup failed for 104.18.6.119: lookup 104.18.6.119: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 104.18.7.119: lookup 104.18.7.119: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 2606:4700::6812:777: lookup 2606:4700::6812:777: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 2606:4700::6812:677: lookup 2606:4700::6812:677: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

B

TLS Certificate Expiry & Recommendations

156 days until leaf cert expires — 2 issues to address

REVIEW

Certificate validity

156

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

B

Operational Status Page

No status page link detected

REVIEW

No status page link detected

No operational status page link detected

Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

CNAME does not point at a known takeover-able service

A+

Multi-Resolver DNS Speed

Mean 29ms across 3 resolvers (spread 9ms)

PASS

Mean 29ms across 3 resolvers (spread 9ms)

Cloudflare: 24ms

Got: 24ms via 1.1.1.1:53

Google: 30ms

Got: 30ms via 8.8.8.8:53

Quad9: 33ms

Got: 33ms via 9.9.9.9:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://www.lycamobile.co.uk/en/

https://www.lycamobile.co.uk/en/

221 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.lycamobile.co.uk/en/	200	221 ms	HTTP/1.1	cloudflare

A+

IPv6 Readiness

IPv6 reachable (17 ms)

PASS

IPv6 reachable (17 ms)

IPv6 is configured and reachable at 2606:4700::6812:777, 2606:4700::6812:677

Got: 17 ms connect

IPv6 Ready

AAAA Records 2606:4700::6812:777, 2606:4700::6812:677 Connection Reachable (17 ms)

A+

Crawlability

robots.txt present, sitemap with 476 URLs

PASS

robots.txt present, sitemap with 476 URLs

robots.txt is present

Got: 188 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 476 entries

robots.txt references sitemap

robots.txt 200 OK

Size 188 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed

User-agent: *

Allow: /


Disallow: /*?*page=

Disallow: *==


#----Sitemaps---

Sitemap: https://www.lycamobile.co.uk/sitemap.xml

Sitemap: https://www.lycamobile.co.uk/blog/sitemap.xml

sitemap.xml 200 OK

Type URL Set URLs 476 entries Valid XML Yes

Sample URLs:

A+

URL Variants

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

PASS

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

www/non-www redirect configured correctly (preferred: www)

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.lycamobile.co.uk/en/

301https://lycamobile.co.uk/en/

Preferred variant: www

Trailing Slash

200https://www.lycamobile.co.uk/en/

308https://www.lycamobile.co.uk/en

HTTP → HTTPS

301http://www.lycamobile.co.uk/en/ → https://www.lycamobile.co.uk/en/

Consistent

A

Domain Intelligence

lycamobile.co.uk — via Key-Systems GmbH, 21 years old, hosted on AWS

PASS

lycamobile.co.uk — via Key-Systems GmbH, 21 years old, hosted on AWS

Domain expires in 82 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Jan 24, 2027

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: Key-Systems GmbH

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.

Hosting: AWS

Got: AS16509

Domain expiry

79 days

January 24, 2027

SSL certificate

156 days

Issued by GoDaddy.com

Domain age

21 years

Registered January 24, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.42.0.52

Registrar

Key-Systems GmbH

Unlocked 5 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the domain or enable auto-renewal to prevent accidental expiry
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Key-Systems GmbH

Created January 24, 2006 (21 years ago)

Expires January 24, 2027 (2 months)

Last Updated January 10, 2026

Name Servers ns1.brandshelter.com., ns2.brandshelter.de., ns3.brandshelter.info., ns4.brandshelter.net., ns5.brandshelter.us.

DNSSEC Not enabled

Hosting

IP Address 13.42.0.52

ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)

Provider AWS

Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

PASS

DNS Lookup

31 ms

TCP Connect

17 ms

TLS Handshake

24 ms

Time to First Byte

194 ms

Total Time

201 ms

Connection waterfall

DNS Lookup 31 ms TCP Connect 17 ms TLS Handshake 24 ms Server Processing 123 ms Content Transfer 6 ms

A

CDN & Delivery

Document and assets on Cloudflare

PASS

Document and assets on Cloudflare

Document is served via Cloudflare CDN (edge: CDG)

Got: delegation www.lycamobile.co.uk.cdn.cloudflare.net

CDN cache status: DYNAMIC

Assets on Cloudflare: cms-assets.ldsvcplatform.com (assets: 67), cache HIT

Got: delegation cms-assets.ldsvcplatform.com.cdn.cloudflare.net

Assets on Cloudflare: pim-assets.ldsvcplatform.com (assets: 6), cache HIT

Got: delegation pim-assets.ldsvcplatform.com.cdn.cloudflare.net

Document served via CDN: Cloudflare

Provider Cloudflare Cache Status DYNAMIC Evidence delegation www.lycamobile.co.uk.cdn.cloudflare.net

Asset hosts on a CDN

cms-assets.ldsvcplatform.com — Cloudflare · assets: 67 · Cache Status: HIT
pim-assets.ldsvcplatform.com — Cloudflare · assets: 6 · Cache Status: HIT

Other asset hosts

assets.adobedtm.com — assets: 2 · below probe threshold
cdn.cookielaw.org — assets: 2 · below probe threshold
www.googletagmanager.com — assets: 2 · below probe threshold
s3-eu-west-2.amazonaws.com — assets: 1 · below probe threshold
sc-static.net — assets: 1 · below probe threshold
scripts.clarity.ms — assets: 1 · below probe threshold
tr.snapchat.com — assets: 1 · below probe threshold
www.clarity.ms — assets: 1 · below probe threshold

A+

CDN Cache Observability

Cache state: DYNAMIC

PASS

Cache state: DYNAMIC

CDN cache state observable via 1 header(s)

Got: cf-cache-status=DYNAMIC

A+

Health Check Endpoint

Health endpoint at https://www.lycamobile.co.uk/health (HTTP 200)

PASS

Health endpoint at https://www.lycamobile.co.uk/health (HTTP 200)

Public health endpoint at https://www.lycamobile.co.uk/health

Got: https://www.lycamobile.co.uk/health