Skip to content
https://www.manikarnikaevents.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 7 REVIEW
B
DNS Records
2 A records, 27 ms lookup
REVIEW
2 A records, 27 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 35.157.26.135, 63.176.8.218
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a05:d014:58f:6200::259, 2a05:d014:58f:6200::258
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: manikarnikaevents.netlify.app
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 27 ms
Got: 27 ms
A35.157.26.135, 63.176.8.218
AAAA2a05:d014:58f:6200::259, 2a05:d014:58f:6200::258
CNAMEmanikarnikaevents.netlify.app
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 27 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)
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/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
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.
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 lookup failed for 2a05:d014:58f:6200::259: lookup 2a05:d014:58f:6200::259: 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 2a05:d014:58f:6200::258: lookup 2a05:d014:58f:6200::258: 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
88 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

88
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
  • 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+
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 29ms across 3 resolvers (spread 13ms)
PASS
Mean 29ms across 3 resolvers (spread 13ms)
Info::
Quad9: 24ms
Got: 24ms via 9.9.9.9:53
Info::
Google: 26ms
Got: 26ms via 8.8.8.8:53
Info::
Cloudflare: 37ms
Got: 37ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.manikarnikaevents.com

https://www.manikarnikaevents.com

294 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.manikarnikaevents.com200294 msHTTP/1.1Netlify
A+
IPv6 Readiness
IPv6 reachable (25 ms)
PASS
IPv6 reachable (25 ms)
Info::
IPv6 is configured and reachable at 2a05:d014:58f:6200::259, 2a05:d014:58f:6200::258
Got: 25 ms connect
IPv6 Ready
AAAA Records 2a05:d014:58f:6200::259, 2a05:d014:58f:6200::258 Connection Reachable (25 ms)
A+
Crawlability
robots.txt present, sitemap with 27 URLs
PASS
robots.txt present, sitemap with 27 URLs
Info::
robots.txt is present
Got: 475 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 27 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 475 B Sitemaps referenced 1 User-agents *, Googlebot Blocking No — crawling allowed
# https://www.robotstxt.org/robotstxt.html
User-agent: *
Allow: /
Disallow: /admin
Disallow: /admin/

# Googlebot specific rules
User-agent: Googlebot
Allow: /
Disallow: /admin
Disallow: /admin/

# AI Agents & Agentic Resource Discovery (ARD) (Discovered via HTTP Link Header & HTML Link tags)
# Agentmap: https://manikarnikaevents.com/.well-known/ard.json
# LLMs: https://manikarnikaevents.com/llms.txt

# Sitemap Location
Sitemap: https://manikarnikaevents.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 27 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: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

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

Preferred variant: www

HTTP → HTTPS

301http://www.manikarnikaevents.com/ → https://www.manikarnikaevents.com/

Consistent

A+
Domain Intelligence
manikarnikaevents.com — via NameCheap, Inc., 1 days old, hosted on AWS
PASS
manikarnikaevents.com — via NameCheap, Inc., 1 days old, hosted on AWS
Info::
Domain registered until Oct 31, 2027 (1 years remaining)
Info::
Domain is only 1 days old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Oct 31, 2026
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: NameCheap, Inc.
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

356 days

October 31, 2027

SSL certificate

88 days

Issued by Let's Encrypt

Domain age

1 days

Registered October 31, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

75.2.60.5

Registrar

NameCheap, Inc.

Unlocked 2 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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar NameCheap, Inc.
Created October 31, 2026 (1 days ago)
Expires October 31, 2027 (1 years)
Last Updated October 31, 2026
Name Servers dns1.registrar-servers.com, dns2.registrar-servers.com
DNSSEC Not enabled
Hosting
IP Address 75.2.60.5
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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 439 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
28 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.
133 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
439 ms
Total Time Total request time from DNS lookup through full response.
440 ms

Connection waterfall

DNS Lookup 28 ms TCP Connect 25 ms TLS Handshake 133 ms Server Processing 254 ms Content Transfer 0 ms
A
CDN & Delivery
Document on Netlify; assets also on Fastly
PASS
Document on Netlify; assets also on Fastly
Info::
Document is served via Netlify CDN
Got: delegation manikarnikaevents.netlify.app
Info::
CDN cache status: "Netlify Edge"; fwd=miss; fwd-status=200; stored
Info::
Assets on Fastly: res.cloudinary.com (assets: 29)
Got: delegation cloudinary.map.fastly.net
Document served via CDN: Netlify
Provider Netlify Cache Status "Netlify Edge"; fwd=miss; fwd-status=200; stored Evidence delegation manikarnikaevents.netlify.app

Asset hosts on a CDN

  • res.cloudinary.com — Fastly · assets: 29
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