Skip to content
https://Celebrade.ie

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
17
6 PASS 10 REVIEW 1 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.Celebrade.ie/
200https://Celebrade.ie/

Inconsistent — duplicate content risk

HTTP → HTTPS

200http://Celebrade.ie/

HTTP version does not redirect to HTTPS

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.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 81.17.252.23 does not match any cert SAN: plsklin23.myhost.ie
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
Redirect Chain
1 redirect(s), 2208 ms total
REVIEW
1 redirect(s), 2208 ms total
Info::
Single redirect
Got: https://Celebrade.ie → https://www.celebrade.ie/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2208 ms total
Got: 2208 ms

https://Celebrade.ie

1027 ms · HTTP/1.1

301

https://www.celebrade.ie/

1182 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://Celebrade.ie3011027 msHTTP/1.1nginx
2https://www.celebrade.ie/2001182 msHTTP/1.1nginx

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
HTTP Probe Timing
Total 948 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
221 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
80 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
84 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
948 ms
Total Time Total request time from DNS lookup through full response.
949 ms

Connection waterfall

DNS Lookup 221 ms TCP Connect 80 ms TLS Handshake 84 ms Server Processing 563 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
58 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
C
CDN & Delivery
Action
Assets on Cloudflare (host cdnjs.cloudflare.com, 4 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host cdnjs.cloudflare.com, 4 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (cdnjs.cloudflare.com, 4 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: cf-ray: a3e23a79cf350c9c-EWR
Info::
Assets on Cloudflare: cdnjs.cloudflare.com (assets: 4), cache BYPASS
Got: cf-ray: a3e23a79cf350c9c-EWR
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • cdnjs.cloudflare.com — Cloudflare · assets: 4 · Cache Status: BYPASS

Other asset hosts

  • www.celebrade.ie — assets: 68 · not attributed
  • fonts.googleapis.com — assets: 4 · Google
  • www.googletagmanager.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
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.
A
DNS Records
1 A records, 219 ms lookup
PASS
1 A records, 219 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 81.17.252.23
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns3.myhostns.com, ns1.myhostns.com, ns2.myhostns.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (219 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 219 ms
A81.17.252.23
AAAA—
CNAME—
NSns3.myhostns.com, ns1.myhostns.com, ns2.myhostns.com
MX
10 mail.Celebrade.ie
TXT
SPF v=spf1 ip4:81.17.252.53 a mx -all
CAALookup not available with standard resolver
Resolved in 219 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

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
Multi-Resolver DNS Speed
Mean 91ms across 3 resolvers (spread 21ms)
PASS
Mean 91ms across 3 resolvers (spread 21ms)
Info::
Cloudflare: 83ms
Got: 83ms via 1.1.1.1:53
Info::
Quad9: 86ms
Got: 86ms via 9.9.9.9:53
Info::
Google: 104ms
Got: 104ms via 8.8.8.8:53
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 322 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 322 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-content/uploads/wc-logs/
Disallow: /wp-content/uploads/woocommerce_transient_files/
Disallow: /wp-content/uploads/woocommerce_uploads/
Disallow: /*?add-to-cart=
Disallow: /*?*add-to-cart=
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://www.celebrade.ie/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
Celebrade.ie — via Myhost.ie, 7 months old, hosted on BLACKNIGHT-AS - Blacknight Internet Solutions Limited, IE
PASS
Celebrade.ie — via Myhost.ie, 7 months old, hosted on BLACKNIGHT-AS - Blacknight Internet Solutions Limited, IE
Info::
Domain registered until Feb 16, 2027 (4 months remaining)
Info::
Registrar: Myhost.ie
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: BLACKNIGHT-AS - Blacknight Internet Solutions Limited, IE
Got: AS39122
Domain expiry

148 days

February 16, 2027

SSL certificate

58 days

Issued by Let's Encrypt

Domain age

7 months

Registered February 16, 2026

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

BLACKNIGHT-AS - Blacknight Internet Solutions Limited, IE

ASN AS39122

81.17.252.23

Registrar

Myhost.ie

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Myhost.ie
Created February 16, 2026 (7 months ago)
Expires February 16, 2027 (4 months)
Last Updated March 2, 2026
Name Servers ns1.myhostns.com, ns2.myhostns.com, ns3.myhostns.com
Hosting
IP Address 81.17.252.23
ASN AS39122 (BLACKNIGHT-AS - Blacknight Internet Solutions Limited, IE)
Provider BLACKNIGHT-AS - Blacknight Internet Solutions Limited, IE
Data source: whois (1.4s)

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+
Health Check Endpoint
Health endpoint at https://Celebrade.ie/health (HTTP 200)
PASS
Health endpoint at https://Celebrade.ie/health (HTTP 200)
Info::
Public health endpoint at https://Celebrade.ie/health
Got: https://Celebrade.ie/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback