Skip to content
https://weezevent.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
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
127 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

127
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
A+
DNS Records
4 A records, 48 ms lookup
PASS
4 A records, 48 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 52.222.132.107, 52.222.132.40, 52.222.132.121, 52.222.132.34
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1044.awsdns-02.org, ns-1752.awsdns-27.co.uk, ns-808.awsdns-37.net, ns-455.awsdns-56.com
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: 48 ms
Got: 48 ms
A52.222.132.107, 52.222.132.40, 52.222.132.121, 52.222.132.34
AAAA—
CNAME—
NSns-1044.awsdns-02.org, ns-1752.awsdns-27.co.uk, ns-808.awsdns-37.net, ns-455.awsdns-56.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
have-i-been-pwned-verification=bb0e86f8f8ec2d7bebf1a900cec34828
Sendinblue-code:929ab8c048a3ae41cbb6d8dc83169e3e
google-site-verification=5oHjwGdBAUjqQ0J_WbleAfcZRY3fb_fjjxSbZn1cZ9w
SPF v=spf1 include:_spf.google.com include:spf.sendinblue.com include:amazonses.com ...
CAALookup not available with standard resolver
Resolved in 48 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
Redirect Chain
1 redirect(s), 84 ms total
PASS
1 redirect(s), 84 ms total
Info::
Single redirect
Got: https://weezevent.com → https://weezevent.com/fr/ (301)

https://weezevent.com

52 ms · HTTP/1.1

301

https://weezevent.com/fr/

32 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://weezevent.com30152 msHTTP/1.1CloudFront
2https://weezevent.com/fr/20032 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 16 URLs
PASS
robots.txt present, sitemap with 16 URLs
Info::
robots.txt is present
Got: 160 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 16 entries
Info::
Sitemap index with 16 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 160 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://weezevent.com/sitemap.xml

Sitemap: https://weezevent.com/sitemap-news.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 16 entries Valid XML Yes
Child Sitemaps:
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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.weezevent.com/
200https://weezevent.com/

Preferred variant: non-www

HTTP → HTTPS

301http://weezevent.com/ → https://weezevent.com/

Consistent

A+
Domain Intelligence
weezevent.com — via Gandi SAS, 18 years, 6 months old, hosted on AWS
PASS
weezevent.com — via Gandi SAS, 18 years, 6 months old, hosted on AWS
Info::
Domain registered until Jan 25, 2029 (2 years, 9 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: Gandi SAS
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

954 days

January 25, 2029

SSL certificate

127 days

Issued by Amazon

Domain age

18 years, 6 months

Registered January 25, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

52.222.132.40

Registrar

Gandi SAS

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 Gandi SAS
Created January 25, 2008 (18 years, 6 months ago)
Expires January 25, 2029 (2 years, 9 months)
Last Updated December 22, 2025
Name Servers ns-1044.awsdns-02.org, ns-1752.awsdns-27.co.uk, ns-455.awsdns-56.com, ns-808.awsdns-37.net
DNSSEC Not enabled
Hosting
IP Address 52.222.132.40
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.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 171 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
47 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
171 ms
Total Time Total request time from DNS lookup through full response.
172 ms

Connection waterfall

DNS Lookup 47 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 121 ms Content Transfer 0 ms
A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: MAD53-P7)
Got: x-amz-cf-id: EitWF7mqCADUT5HO5ODtXj36XtEuWml6749SizOLmnd_QN-UyaMmNg==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: EitWF7mqCADUT5HO5ODtXj36XtEuWml6749SizOLmnd_QN-UyaMmNg==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback