Skip to content
https://atl30309.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Amsterdam, Netherlands
302 Found
Checks
17
8 PASS 8 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

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

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 195.201.125.205 does not match any cert SAN: static.205.125.201.195.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.
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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

52
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+
DNS Records
1 A records, 8 ms lookup
PASS
1 A records, 8 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 195.201.125.205
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: dns1.registrar-servers.com, dns2.registrar-servers.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 8 ms
Got: 8 ms
A195.201.125.205
AAAA
CNAME
NSdns1.registrar-servers.com, dns2.registrar-servers.com
MX
10 mail.protonmail.ch
20 mailsec.protonmail.ch
TXT
SPF v=spf1 include:_spf.protonmail.ch mx ~all
protonmail-verification=4e64d3ab0b0e554a7c481f088a335d2a4e3caa72
CAALookup not available with standard resolver
Resolved in 8 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

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+
Multi-Resolver DNS Speed
Mean 10ms across 3 resolvers (spread 24ms)
PASS
Mean 10ms across 3 resolvers (spread 24ms)
Info::
Cloudflare: 1ms
Got: 1ms via 1.1.1.1:53
Info::
Quad9: 5ms
Got: 5ms via 9.9.9.9:53
Info::
Google: 25ms
Got: 25ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 133 ms total
PASS
1 redirect(s), 133 ms total
Info::
Single redirect
Got: https://atl30309.com → https://element.atl30309.com (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://atl30309.com
Info::
Cross-domain redirect detected

https://atl30309.com

60 ms · HTTP/1.1

302

https://element.atl30309.com

73 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://atl30309.com30260 msHTTP/1.1
2https://element.atl30309.com20073 msHTTP/1.1nginx/1.29.5

See the visual redirect chain in the HTTP Probe tab →

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

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.atl30309.com/
200https://atl30309.com/

HTTP → HTTPS

301http://atl30309.com/ https://atl30309.com/

Consistent

A+
Domain Intelligence
atl30309.com — via NameCheap, Inc., 7 years, 1 months old, hosted on Hetzner
PASS
atl30309.com — via NameCheap, Inc., 7 years, 1 months old, hosted on Hetzner
Info::
Domain registered until Apr 17, 2027 (11 months remaining)
Info::
DNSSEC is enabled
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: Hetzner
Got: AS24940
Domain expiry

335 days

April 17, 2027

SSL certificate

52 days

Issued by Let's Encrypt

Domain age

7 years, 1 months

Registered April 17, 2019

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Hetzner

ASN AS24940

195.201.125.205

Registrar

NameCheap, 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 NameCheap, Inc.
Created April 17, 2019 (7 years, 1 months ago)
Expires April 17, 2027 (11 months)
Last Updated March 18, 2026
Name Servers dns1.registrar-servers.com, dns2.registrar-servers.com
DNSSEC Enabled
Hosting
IP Address 195.201.125.205
ASN AS24940 (HETZNER-AS, DE)
Provider Hetzner
Data source: rdap (0.9s)

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

Connection waterfall

DNS Lookup 16 ms TCP Connect 11 ms TLS Handshake 34 ms Server Processing 11 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