Skip to content
https://Makenaevents.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
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.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 63.176.8.218 does not match any cert SAN: ec2-63-176-8-218.eu-central-1.compute.amazonaws.com
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.
Info::
PTR for 35.157.26.135 does not match any cert SAN: ec2-35-157-26-135.eu-central-1.compute.amazonaws.com
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.
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
35 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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: 404, /healthz: 404, /ping: 404, /status: 404.
A
DNS Records
2 A records, 1039 ms lookup
PASS
2 A records, 1039 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 63.176.8.218, 35.157.26.135
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: dns1.p03.nsone.net, dns4.p03.nsone.net, dns3.p03.nsone.net, dns2.p03.nsone.net
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (1039 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1039 ms
A63.176.8.218, 35.157.26.135
AAAA—
CNAME—
NSdns1.p03.nsone.net, dns4.p03.nsone.net, dns3.p03.nsone.net, dns2.p03.nsone.net
MX
0 makenaevents-com.mail.protection.outlook.com
10 inbound-smtp.us-east-1.amazonaws.com
TXT
google-site-verification=t4EXQ-qpyUKV0LR9m7n20HrAdMex90Rw3ljQeqH99Hw
SPF v=spf1 include:secureserver.net -all
MS=ms83910947
CAALookup not available with standard resolver
Resolved in 1039 ms

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 30ms across 3 resolvers (spread 12ms)
PASS
Mean 30ms across 3 resolvers (spread 12ms)
Info::
Google: 25ms
Got: 25ms via 8.8.8.8:53
Info::
Cloudflare: 28ms
Got: 28ms via 1.1.1.1:53
Info::
Quad9: 37ms
Got: 37ms 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://Makenaevents.com

https://Makenaevents.com

386 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://Makenaevents.com200386 msHTTP/1.1Netlify
A+
Crawlability
robots.txt present, sitemap with 9 URLs
PASS
robots.txt present, sitemap with 9 URLs
Info::
robots.txt is present
Got: 70 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 70 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /

Sitemap: https://makenaevents.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 9 entries Valid XML Yes
Sample URLs:
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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

301http://Makenaevents.com/ → https://makenaevents.com/

Consistent

A
Domain Intelligence
Makenaevents.com — via GoDaddy.com, LLC, 9 months old, hosted on AWS
PASS
Makenaevents.com — via GoDaddy.com, LLC, 9 months old, hosted on AWS
Warning::
Domain expires in 70 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jan 18, 2027
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: GoDaddy.com, LLC
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

70 days

January 18, 2027

SSL certificate

35 days

Issued by Let's Encrypt

Domain age

9 months

Registered January 18, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

35.157.26.135

Registrar

GoDaddy.com, LLC

Unlocked 4 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 GoDaddy.com, LLC
Created January 18, 2026 (9 months ago)
Expires January 18, 2027 (2 months)
Last Updated January 18, 2026
Name Servers dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net
DNSSEC Not enabled
Hosting
IP Address 35.157.26.135
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 44 ms TCP Connect 25 ms TLS Handshake 139 ms Server Processing 403 ms Content Transfer 24 ms
A
CDN & Delivery
Netlify ("Netlify Edge"; fwd=miss; fwd-status=200; stored)
PASS
Netlify ("Netlify Edge"; fwd=miss; fwd-status=200; stored)
Info::
Document is served via Netlify CDN
Got: x-nf-request-id: 01M701695X70D7TMQAQT2WT42E
Info::
CDN cache status: "Netlify Edge"; fwd=miss; fwd-status=200; stored
Document served via CDN: Netlify
Provider Netlify Cache Status "Netlify Edge"; fwd=miss; fwd-status=200; stored Evidence x-nf-request-id: 01M701695X70D7TMQAQT2WT42E
A+
CDN Cache Observability
Cache state: fresh (Age=0)
PASS
Cache state: fresh (Age=0)
Info::
CDN cache state observable via 1 header(s)
Got: age=0
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback