Skip to content
https://popdel.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
6 PASS 10 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
Got: document origin: Hetzner
No CDN (document or assets)
Document origin Hetzner

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNS Records
1 A records, 214 ms lookup
REVIEW
1 A records, 214 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 89.167.92.147
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: launch1.spaceship.net, launch2.spaceship.net
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'.
Warning::
DNS resolution is slow (214 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 214 ms
A89.167.92.147
AAAA—
CNAME—
NSlaunch1.spaceship.net, launch2.spaceship.net
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 214 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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)

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

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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 89.167.92.147 does not match any cert SAN: static.147.92.167.89.clients.your-server.de
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.
B
Multi-Resolver DNS Speed
Mean 72ms across 3 resolvers (spread 191ms)
REVIEW
Mean 72ms across 3 resolvers (spread 191ms)
Info::
Quad9: 0ms
Got: 0ms via 9.9.9.9:53
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
Info::
Cloudflare: 191ms
Got: 191ms via 1.1.1.1:53
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.popdel.com/
200https://popdel.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B
TLS Certificate Expiry & Recommendations
48 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
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
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::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (ECDSAP256SHA256)
A
Redirect Chain
1 redirect(s), 887 ms total
PASS
1 redirect(s), 887 ms total
Info::
Single redirect
Got: https://popdel.com → https://www.popdel.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 887 ms total
Got: 887 ms

https://popdel.com

157 ms · HTTP/1.1

301

https://www.popdel.com/

730 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://popdel.com301157 msHTTP/1.1nginx/1.24.0 (Ubuntu)
2https://www.popdel.com/200730 msHTTP/1.1nginx/1.24.0 (Ubuntu)

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 91 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 91 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /museum
Sitemap: https://www.popdel.com/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
popdel.com — via Spaceship, Inc., 4 years, 1 months old, hosted on Hetzner
PASS
popdel.com — via Spaceship, Inc., 4 years, 1 months old, hosted on Hetzner
Info::
Domain registered until Aug 7, 2027 (10 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Spaceship, 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: Hetzner
Got: AS24940
Domain expiry

320 days

August 7, 2027

SSL certificate

48 days

Issued by Let's Encrypt

Domain age

4 years, 1 months

Registered August 7, 2022

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Hetzner

ASN AS24940

89.167.92.147

Registrar

Spaceship, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Spaceship, Inc.
Created August 7, 2022 (4 years, 1 months ago)
Expires August 7, 2027 (10 months)
Last Updated August 5, 2026
Name Servers launch1.spaceship.net, launch2.spaceship.net
DNSSEC Enabled
Hosting
IP Address 89.167.92.147
ASN AS24940 (HETZNER-AS - Hetzner Online GmbH, DE)
Provider Hetzner
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 287 ms TCP Connect 48 ms TLS Handshake 52 ms Server Processing 48 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback