Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Madrid, Spain

301 Moved Permanently

Checks

7 PASS 8 REVIEW 2 FIX

Multi-Resolver DNS Speed

Action

Mean 425ms across 3 resolvers (spread 1213ms)

FIX

Mean 425ms across 3 resolvers (spread 1213ms)

Cloudflare: 17ms

Got: 17ms via 1.1.1.1:53

Google: 28ms

Got: 28ms via 8.8.8.8:53

Quad9: 1230ms

Got: 1230ms via 9.9.9.9:53

High latency spread between resolvers: 1213ms (min 17ms / max 1230ms)

Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.

Redirect Chain

Action

2 redirect(s), 1083 ms total

FIX

2 redirect(s), 1083 ms total

2 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://www.evilangel.com/

Redirect overhead: 1083 ms total

Got: 1083 ms

https://evilangel.com

67 ms · HTTP/1.1

301

https://www.evilangel.com/

346 ms · HTTP/1.1

302

https://www.evilangel.com/sfw

671 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://evilangel.com	301	67 ms	HTTP/1.1	cloudflare
2	https://www.evilangel.com/	302	346 ms	HTTP/1.1	cloudflare
3	https://www.evilangel.com/sfw	200	671 ms	HTTP/1.1	cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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).

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.

Reverse DNS

Action

0/3 IPs match cert SAN

REVIEW

0/3 IPs match cert SAN

PTR lookup failed for 104.26.12.149: lookup 104.26.12.149: 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.71.41: lookup 172.67.71.41: 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 104.26.13.149: lookup 104.26.13.149: 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.

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

TLS Certificate Expiry & Recommendations

41 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

days left

0d 30d 60d 90d+

Recommended actions

Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
Add includeSubDomains to the HSTS directive
Enable DNSSEC on your domain for DNS spoofing protection

CDN & Delivery

Cloudflare

REVIEW

Cloudflare

Site is served via Cloudflare CDN (edge: CDG)

Got: cf-ray: a18de9948d34d6c2-CDG

CDN Detected: Cloudflare

Provider Cloudflare Evidence cf-ray: a18de9948d34d6c2-CDG

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.

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.

A+

DNS Records

3 A records, 38 ms lookup

PASS

3 A records, 38 ms lookup

Resolves to 3 IPv4 address(es)

Got: 104.26.12.149, 172.67.71.41, 104.26.13.149

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: noah.ns.cloudflare.com, elsa.ns.cloudflare.com

5 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 38 ms

Got: 38 ms

A	104.26.12.149, 172.67.71.41, 104.26.13.149
AAAA	—
CNAME	—
NS	noah.ns.cloudflare.com, elsa.ns.cloudflare.com
MX	1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx3.googlemail.com 10 aspmx2.googlemail.com
TXT	google-site-verification=1Y4rRgjyFPf2qIwGVXGHo0ifGxGNA1To6v9o2AOwZ4w IPROTA_D23669-XXX.TXT SPF v=spf1 ip4:24.43.139.227 include:_spf.google.com ~all google-site-verification=oVGODYMVHs8nYjxHV7S2mblHoV68L7mfvaIVa4AMRu0 amazonses:3GddFvA79k5XG3BheoL93eZ7nj4WRpTS5t+6RomojTo= mailru-verification: d81bf3fd4ea27634
CAA	Lookup not available with standard resolver

Resolved in 38 ms

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Crawlability

robots.txt present, sitemap with 5 URLs

PASS

robots.txt present, sitemap with 5 URLs

robots.txt is present

Got: 4831 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 5 entries

robots.txt references sitemap

robots.txt 200 OK

Size 4831 B Sitemaps referenced 83 User-agents * Blocking No — crawling allowed

User-agent: *

Disallow: /ratings/actor*

Disallow: /media/signPhotoset*

Sitemap: https://www.evilangel.com/sitemap/main.xml

Sitemap: https://xmlsitemap.evilangel.com/evilangel_20220805.xml 

Sitemap: https://www.evilangel.com/sitemap/actor-1.xml

Sitemap: https://www.evilangel.com/sitemap/actor-2.xml

Sitemap: https://www.evilangel.com/sitemap/actor-3.xml

Sitemap: https://www.evilangel.com/sitemap/actor-4.xml

Sitemap: https://www.evilangel.com/sitemap/actor-5.xml

Sitemap: https://www.evilangel.com/sitemap/actor-6.xml

Sitemap: https://www.evilangel.com/sitemap/actor-7.xml

Sitemap: https://www.evilangel.com/sitemap/actor-8.xml

Sitemap: https://www.evilangel.com/sitemap/actor-9.xml

Sitemap: https://www.evilangel.com/sitemap/scene-1.xml

Sitemap: https://www.evilangel.com/sitemap/scene-2.xml

Sitemap: https://www.evilangel.com/sitemap/scene-3.xml

Sitemap: https://www.evilangel.com/sitemap/scene-4.xml

Sitemap: https://www.evilangel.com/sitemap/scene-5.xml

Sitemap: https://www.evilangel.com/sitemap/scene-6.xml

Sitemap: https://www.evilangel.com/sitemap/scene-7.xml

Sitemap: https://www.evilangel.com/sitemap/scene-8.xml

Sitemap: https://www.evilangel.com/sitemap/scene-9.xml

Sitemap: https://www.evilangel.com/sitemap/scene-10.xml

Sitemap: https://www.evilangel.com/sitemap/scene-11.xml

Sitemap: https://www.evilangel.com/sitemap/scene-12.xml

Sitemap: https://www.evilangel.com/sitemap/scene-13.xml

Sitemap: https://www.evilangel.com/sitemap/scene-14.xml

Sitemap: https://www.evilangel.com/sitemap/scene-15.xml

Sitemap: https://www.evilangel.com/sitemap/scene-16.xml

Sitemap: https://www.evilangel.com/sitemap/scene-17.xml

Sitemap: https://www.evilangel.com/sitemap/scene-18.xml

Sitemap: https://www.evilangel.com/sitemap/scene-19.xml

Sitemap: https://www.evilangel.com/sitemap/scene-20.xml

Sitemap: https://www.evilangel.com/sitemap/scene-21.xml

Sitemap: https://www.evilangel.com/sitemap/scene-22.xml

Sitemap: https://www.evilangel.com/sitemap/scene-23.xml

Sitemap: https://www.evilangel.com/sitemap/scene-24.xml

Sitemap: https://www.evilangel.com/sitemap/scene-25.xml

Sitemap: https://www.evilangel.com/sitemap/scene-26.xml

Sitemap: https://www.evilangel.com/sitemap/scene-27.xml

Sitemap: https://www.evilangel.com/sitemap/scene-28.xml

Sitemap: https://www.evilangel.com/sitemap/scene-29.xml

Sitemap: https://www.evilangel.com/sitemap/scene-30.xml

Sitemap: https://www.evilangel.com/sitemap/scene-31.xml

Sitemap: https://www.evilangel.com/sitemap/scene-32.xml

Sitemap: https://www.evilangel.com/sitemap/scene-33.xml

Sitemap: https://www.evilangel.com/sitemap/scene-34.xml

Sitemap: https://www.evilangel.com/sitemap/scene-35.xml

Sitemap: https://www.evilangel.com/sitemap/scene-36.xml

Sitemap: https://www.evilangel.com/sitemap/scene-37.xml

Sitemap: https://www.evilangel.com/sitemap/scene-38.xml

Sitemap: https://www.evilangel.com/sitemap/scene-39.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-1.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-2.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-3.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-4.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-5.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-6.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-7.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-8.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-9.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-10.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-11.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-12.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-13.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-14.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-15.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-16.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-17.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-18.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-19.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-20.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-21.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-22.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-23.xml

Sitemap: https://www.evilangel.com/sitemap/photoset-24.xml

Sitemap: https://www.evilangel.com/sitemap/dvd-1.xml

Sitemap: https://www.evilangel.com/sitemap/dvd-2.xml

Sitemap: https://www.evilangel.com/sitemap/dvd-3.xml

Sitemap: https://www.evilangel.com/sitemap/dvd-4.xml

Sitemap: https://www.evilangel.com/sitemap/dvd-5.xml

Sitemap: https://www.evilangel.com/sitemap/dvd-6.xml

Sitemap: https://www.evilangel.com/sitemap/dvd-7.xml

Sitemap: https://www.evilangel.com/sitemap/dvd-8.xml

Sitemap: https://www.evilangel.com/sitemap/dvd-9.xml

sitemap.xml 200 OK

Type URL Set URLs 5 entries Valid XML Yes

Sample URLs:

A+

URL Variants

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

PASS

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

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.evilangel.com/

200https://evilangel.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+

Domain Intelligence

evilangel.com — via EuroDNS S.A., 30 years, 6 months old, hosted on Cloudflare

PASS

evilangel.com — via EuroDNS S.A., 30 years, 6 months old, hosted on Cloudflare

Domain registered until Jun 9, 2027 (11 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: EuroDNS S.A.

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.

Hosting: Cloudflare

Got: AS13335

Domain expiry

332 days

June 9, 2027

SSL certificate

41 days

Issued by Google Trust Services

Domain age

30 years, 6 months

Registered June 10, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.26.12.149

Registrar

EuroDNS S.A.

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 EuroDNS S.A.

Created June 10, 1996 (30 years, 6 months ago)

Expires June 9, 2027 (11 months)

Last Updated April 22, 2026

Name Servers elsa.ns.cloudflare.com, noah.ns.cloudflare.com

DNSSEC Not enabled

Hosting

IP Address 104.26.12.149

ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)

Provider Cloudflare

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

PASS

DNS Lookup

38 ms

TCP Connect

17 ms

TLS Handshake

25 ms

Time to First Byte

108 ms

Total Time

108 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 17 ms TLS Handshake 25 ms Server Processing 28 ms Content Transfer 0 ms

A+

Health Check Endpoint

Health endpoint at https://evilangel.com/health (HTTP 200)

PASS

Health endpoint at https://evilangel.com/health (HTTP 200)

Public health endpoint at https://evilangel.com/health

Got: https://evilangel.com/health

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.