Infrastructure - https://www.tsevilangel.com BeaverCheck Audit

B

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

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)

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/4 IPs match cert SAN

REVIEW

0/4 IPs match cert SAN

PTR lookup failed for 104.21.35.169: lookup 104.21.35.169: 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.

PTR lookup failed for 172.67.177.175: lookup 172.67.177.175: 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.

PTR lookup failed for 2606:4700:3031::6815:23a9: lookup 2606:4700:3031::6815:23a9: 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.

PTR lookup failed for 2606:4700:3037::ac43:b1af: lookup 2606:4700:3037::ac43:b1af: 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

67 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

67

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

CDN & Delivery

Document on Cloudflare; assets also on AWS CloudFront

REVIEW

Document on Cloudflare; assets also on AWS CloudFront

Document is served via Cloudflare CDN (edge: CDG)

Got: cf-ray: a57fb8c6cc35702a-CDG

Assets on AWS CloudFront: transform.gammacdn.com (assets: 23), cache Hit from cloudfront

Got: delegation d3e2h8jk1z033l.cloudfront.net

Document served via CDN: Cloudflare

Provider Cloudflare Evidence cf-ray: a57fb8c6cc35702a-CDG

Asset hosts on a CDN

transform.gammacdn.com — AWS CloudFront · assets: 23 · Cache Status: Hit from cloudfront

B

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

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

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

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, 134 ms lookup

PASS

2 A records, 134 ms lookup

Resolves to 2 IPv4 address(es)

Got: 104.21.35.169, 172.67.177.175

Has 2 IPv6 (AAAA) record(s)

Got: 2606:4700:3031::6815:23a9, 2606:4700:3037::ac43:b1af

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution time: 134 ms

Got: 134 ms

A	104.21.35.169, 172.67.177.175
AAAA	2606:4700:3031::6815:23a9, 2606:4700:3037::ac43:b1af
CNAME	—
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 134 ms

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)

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 40ms across 3 resolvers (spread 32ms)

PASS

Mean 40ms across 3 resolvers (spread 32ms)

Google: 27ms

Got: 27ms via 8.8.8.8:53

Cloudflare: 35ms

Got: 35ms via 1.1.1.1:53

Quad9: 59ms

Got: 59ms via 9.9.9.9:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://www.tsevilangel.com

https://www.tsevilangel.com

209 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.tsevilangel.com	200	209 ms	HTTP/1.1	cloudflare

A+

IPv6 Readiness

IPv6 reachable (17 ms)

PASS

IPv6 reachable (17 ms)

IPv6 is configured and reachable at 2606:4700:3031::6815:23a9, 2606:4700:3037::ac43:b1af

Got: 17 ms connect

IPv6 Ready

AAAA Records 2606:4700:3031::6815:23a9, 2606:4700:3037::ac43:b1af Connection Reachable (17 ms)

A+

Crawlability

robots.txt present, sitemap with 6 URLs

PASS

robots.txt present, sitemap with 6 URLs

robots.txt is present

Got: 2914 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 6 entries

Sitemap index with 6 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 2914 B Sitemaps referenced 3 User-agents Baiduspider, Cotoyogi, ICC-Crawler, FishBot, KimiBot, Google-Extended, MistralAI-Training, GoogleOther, Google-CloudVertexBot, QualifiedBot, atlassian-bot, BorderxBot, Bytespider, CCBot, WARDBot, Diffbot, GPTBot, Claude-Web, meta-externalagent, Amazonbot, CitibotSiteCrawler, AwarioRssBot, SemrushBot-SWA, ClaudeBot, anthropic-ai, cohere-ai, PetalBot, AwarioSmartBot, *, Applebot-Extended, NavuBot, magpie-crawler, omgili Blocking No — crawling allowed

# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.
# use:      how AI systems may consume the content (immediate, reference, or full).

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

# BEGIN Cloudflare Managed content


User-agent: *
Content-Signal: search=yes,ai-train=no,use=reference
Allow: /

# Training crawlers
User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: omgili
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: MistralAI-Training
Disallow: /

User-agent: meta-externalagent
Disallow: /

User-agent: GoogleOther
Disallow: /

User-agent: Baiduspider
Disallow: /

User-agent: PetalBot
Disallow: /

User-agent: AwarioSmartBot
User-agent: AwarioRssBot
Disallow: /

User-agent: Google-CloudVertexBot
Disallow: /

User-agent: QualifiedBot
Disallow: /

User-agent: Cotoyogi
Disallow: /

User-agent: ICC-Crawler
Disallow: /

User-agent: atlassian-bot
Disallow: /

User-agent: FishBot
Disallow: /

User-agent: BorderxBot
Disallow: /

User-agent: NavuBot
Disallow: /

User-agent: SemrushBot-SWA
Disallow: /

User-agent: WARDBot
Disallow: /

User-agent: magpie-crawler
Disallow: /

User-agent: KimiBot
Disallow: /

User-agent: CitibotSiteCrawler
Disallow: /

# END Cloudflare Managed Content

User-Agent: *
Allow: /
Disallow: /_next/
Disallow: /api/
Disallow: /*.json$

Sitemap: https://www.tsevilangel.com/sitemap.xml
Sitemap: https://www.tsevilangel.com/sitemap-videos.xml
Sitemap: https://www.tsevilangel.com/sitemap-actors.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 6 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.tsevilangel.com/

https://tsevilangel.com/

HTTP → HTTPS

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

Consistent

A+

Domain Intelligence

tsevilangel.com — via Cloudflare, Inc., 11 years, 7 months old

PASS

tsevilangel.com — via Cloudflare, Inc., 11 years, 7 months old

Domain registered until May 27, 2027 (6 months remaining)

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.

Registrar: Cloudflare, Inc.

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.

Domain expiry

198 days

May 27, 2027

SSL certificate

67 days

Issued by Google Trust Services

Domain age

11 years, 7 months

Registered May 27, 2015

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

Registrar

Cloudflare, 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
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Cloudflare, Inc.

Created May 27, 2015 (11 years, 7 months ago)

Expires May 27, 2027 (6 months)

Last Updated November 6, 2025

Name Servers aiden.ns.cloudflare.com, sara.ns.cloudflare.com

DNSSEC Not enabled

Data source: rdap (0.1s)

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 322 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

39 ms

TCP Connect

17 ms

TLS Handshake

28 ms

Time to First Byte

248 ms

Total Time

322 ms

Connection waterfall

DNS Lookup 39 ms TCP Connect 17 ms TLS Handshake 28 ms Server Processing 164 ms Content Transfer 75 ms