Skip to content
https://www.eapollowholesale.co.uk

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
10 PASS 7 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
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)
Info::
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/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 104.16.81.94: lookup 104.16.81.94: 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.
Info::
PTR lookup failed for 104.16.82.94: lookup 104.16.82.94: 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.
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
TLS Certificate Expiry & Recommendations
33 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: connection error, /healthz: connection error, /ping: connection error, /status: 404.
A
DNS Records
2 A records, 24 ms lookup
PASS
2 A records, 24 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.16.81.94, 104.16.82.94
Info::
No IPv6 (AAAA) records
Warning::
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: eapollowholesale.co.uk
Info::
4 nameserver(s) configured
Got: ns4.nexcess.net, ns2.nexcess.net, ns1.nexcess.net, ns3.nexcess.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 24 ms
Got: 24 ms
A104.16.81.94, 104.16.82.94
AAAA
CNAMEeapollowholesale.co.uk
NSns4.nexcess.net, ns2.nexcess.net, ns1.nexcess.net, ns3.nexcess.net
MX
10 mail.eapollo.co.uk
TXT
SPF v=spf1 +a +mx +ip4:165.84.217.29 include:relay.mailchannels.net ~all
CAALookup not available with standard resolver
Resolved in 24 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

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Multi-Resolver DNS Speed
Mean 16ms across 3 resolvers (spread 26ms)
PASS
Mean 16ms across 3 resolvers (spread 26ms)
Info::
Cloudflare: 6ms
Got: 6ms via 1.1.1.1:53
Info::
Google: 10ms
Got: 10ms via 8.8.8.8:53
Info::
Quad9: 32ms
Got: 32ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.eapollowholesale.co.uk

https://www.eapollowholesale.co.uk

443 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.eapollowholesale.co.uk200443 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 1398 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1398 B Sitemaps referenced 1 User-agents Googlebot-image, *, Googlebot Blocking No — crawling allowed
# Define user agents/bots

User-agent: *

User-agent: Googlebot

User-agent: Googlebot-image


# Urls with parameters

Disallow: /*?

Allow: /*?page=

Allow: /*?p=

Allow: /graphql?

Disallow: /*SID=


# Technical paths

Disallow: /repo/

Disallow: /catalog/product_compare/

Disallow: /catalog/category/view/

Disallow: /catalog/product/view/

Disallow: /catalog/seo_sitemap/

Disallow: /catalogsearch/

Disallow: /mfproductsearch/

Disallow: /checkout/

Disallow: /control/

Disallow: /customer/

Disallow: /customize/

Disallow: /sendfriend/

Disallow: /ajaxcart/

Disallow: /ajax/

Disallow: /quickview/

Disallow: /productalert/

Disallow: /mfcmsdr/

Disallow: /sales/guest/form/

Disallow: /sales/guest/form/

Disallow: /review/

Disallow: /downloadable/

Disallow: /pslogin

Disallow: /subscription

Disallow: /newsletter

Disallow: /push_notification


# Files

Disallow: /index.php

Disallow: /cron.php

Disallow: /cron.sh

Disallow: /error_log

Disallow: /install.php

Disallow: /LICENSE.html

Disallow: /LICENSE.txt

Disallow: /LICENSE_AFL.txt

Disallow: /STATUS.txt

Disallow: /get.php

Disallow: /app/

Disallow: /lib/

Disallow: /*.php$

Disallow: /pkginfo/

Disallow: /report/

Disallow: /var/


#CMS Pages

Disallow: /privacy-policy-cookie-restriction-mode

Disallow: /no-route

Disallow: /enable-cookies

Disallow: /home
Sitemap: https://www.eapollowholesale.co.uk/sitemap.xml

A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Warning::
HTTP→HTTPS redirect is not permanent
Got: HTTP 302 Expected: 301 or 308 permanent redirect

www / non-www

200https://www.eapollowholesale.co.uk/
302https://eapollowholesale.co.uk/

Preferred variant: www

HTTP → HTTPS

302http://www.eapollowholesale.co.uk/ https://www.eapollowholesale.co.uk/

Use a permanent redirect (301 or 308) instead of a temporary one

A+
Domain Intelligence
eapollowholesale.co.uk — via 123-Reg Limited t/a 123-reg, 15 years, 5 months old, hosted on Cloudflare
PASS
eapollowholesale.co.uk — via 123-Reg Limited t/a 123-reg, 15 years, 5 months old, hosted on Cloudflare
Info::
Domain registered until Jun 23, 2030 (3 years, 10 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: 123-Reg Limited t/a 123-reg
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: Cloudflare
Got: AS13335
Domain expiry

1381 days

June 23, 2030

SSL certificate

33 days

Issued by Let's Encrypt

Domain age

15 years, 5 months

Registered June 23, 2011

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.16.81.94

Registrar

123-Reg Limited t/a 123-reg

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 123-Reg Limited t/a 123-reg
Created June 23, 2011 (15 years, 5 months ago)
Expires June 23, 2030 (3 years, 10 months)
Last Updated June 29, 2025
Name Servers ns1.nexcess.net., ns2.nexcess.net., ns3.nexcess.net., ns4.nexcess.net.
DNSSEC Not enabled
Hosting
IP Address 104.16.81.94
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.9s)

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

Connection waterfall

DNS Lookup 21 ms TCP Connect 2 ms TLS Handshake 15 ms Server Processing 319 ms Content Transfer 35 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Document is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: a387c38679a0a364-SJC
Info::
CDN cache status: DYNAMIC
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a387c38679a0a364-SJC
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback