Skip to content
https://www.party-schlaudt.de

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 7 REVIEW
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/12 IPs match cert SAN
REVIEW
0/12 IPs match cert SAN
Info::
PTR for 13.33.153.24 does not match any cert SAN: server-13-33-153-24.lhr3.r.cloudfront.net
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 13.33.153.29 does not match any cert SAN: server-13-33-153-29.lhr3.r.cloudfront.net
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 13.33.153.97 does not match any cert SAN: server-13-33-153-97.lhr3.r.cloudfront.net
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 13.33.153.123 does not match any cert SAN: server-13-33-153-123.lhr3.r.cloudfront.net
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 2600:9000:2021:2c00:15:fa36:9e80:93a1: lookup 2600:9000:2021:2c00:15:fa36:9e80:93a1: 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 2600:9000:2021:a800:15:fa36:9e80:93a1: lookup 2600:9000:2021:a800:15:fa36:9e80:93a1: 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 2600:9000:2021:a000:15:fa36:9e80:93a1: lookup 2600:9000:2021:a000:15:fa36:9e80:93a1: 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 2600:9000:2021:5400:15:fa36:9e80:93a1: lookup 2600:9000:2021:5400:15:fa36:9e80:93a1: 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 2600:9000:2021:7000:15:fa36:9e80:93a1: lookup 2600:9000:2021:7000:15:fa36:9e80:93a1: 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 2600:9000:2021:7a00:15:fa36:9e80:93a1: lookup 2600:9000:2021:7a00:15:fa36:9e80:93a1: 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 2600:9000:2021:fc00:15:fa36:9e80:93a1: lookup 2600:9000:2021:fc00:15:fa36:9e80:93a1: 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 2600:9000:2021:c200:15:fa36:9e80:93a1: lookup 2600:9000:2021:c200:15:fa36:9e80:93a1: 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
Multi-Resolver DNS Speed
Mean 119ms across 3 resolvers (spread 77ms)
REVIEW
Mean 119ms across 3 resolvers (spread 77ms)
Info::
Google: 91ms
Got: 91ms via 8.8.8.8:53
Info::
Cloudflare: 99ms
Got: 99ms via 1.1.1.1:53
Info::
Quad9: 168ms
Got: 168ms via 9.9.9.9:53
B
TLS Certificate Expiry & Recommendations
97 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

97
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
DNS Records
4 A records, 37 ms lookup
PASS
4 A records, 37 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 13.33.153.24, 13.33.153.29, 13.33.153.97, 13.33.153.123
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:2021:2c00:15:fa36:9e80:93a1, 2600:9000:2021:a800:15:fa36:9e80:93a1, 2600:9000:2021:a000:15:fa36:9e80:93a1, 2600:9000:2021:5400:15:fa36:9e80:93a1, 2600:9000:2021:7000:15:fa36:9e80:93a1, 2600:9000:2021:7a00:15:fa36:9e80:93a1, 2600:9000:2021:fc00:15:fa36:9e80:93a1, 2600:9000:2021:c200:15:fa36:9e80:93a1
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: p25554.my.plentysystems.com
Info::
4 nameserver(s) configured
Got: ns-1397.awsdns-46.org, ns-337.awsdns-42.com, ns-564.awsdns-06.net, ns-1743.awsdns-25.co.uk
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: 37 ms
Got: 37 ms
A13.33.153.24, 13.33.153.29, 13.33.153.97, 13.33.153.123
AAAA2600:9000:2021:2c00:15:fa36:9e80:93a1, 2600:9000:2021:a800:15:fa36:9e80:93a1, 2600:9000:2021:a000:15:fa36:9e80:93a1, 2600:9000:2021:5400:15:fa36:9e80:93a1, 2600:9000:2021:7000:15:fa36:9e80:93a1, 2600:9000:2021:7a00:15:fa36:9e80:93a1, 2600:9000:2021:fc00:15:fa36:9e80:93a1, 2600:9000:2021:c200:15:fa36:9e80:93a1
CNAMEp25554.my.plentysystems.com
NSns-1397.awsdns-46.org, ns-337.awsdns-42.com, ns-564.awsdns-06.net, ns-1743.awsdns-25.co.uk
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 37 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)

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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.party-schlaudt.de

https://www.party-schlaudt.de

144 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.party-schlaudt.de200144 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (25 ms)
PASS
IPv6 reachable (25 ms)
Info::
IPv6 is configured and reachable at 2600:9000:2021:2c00:15:fa36:9e80:93a1, 2600:9000:2021:a800:15:fa36:9e80:93a1, 2600:9000:2021:a000:15:fa36:9e80:93a1, 2600:9000:2021:5400:15:fa36:9e80:93a1, 2600:9000:2021:7000:15:fa36:9e80:93a1, 2600:9000:2021:7a00:15:fa36:9e80:93a1, 2600:9000:2021:fc00:15:fa36:9e80:93a1, 2600:9000:2021:c200:15:fa36:9e80:93a1
Got: 25 ms connect
IPv6 Ready
AAAA Records 2600:9000:2021:2c00:15:fa36:9e80:93a1, 2600:9000:2021:a800:15:fa36:9e80:93a1, 2600:9000:2021:a000:15:fa36:9e80:93a1, 2600:9000:2021:5400:15:fa36:9e80:93a1, 2600:9000:2021:7000:15:fa36:9e80:93a1, 2600:9000:2021:7a00:15:fa36:9e80:93a1, 2600:9000:2021:fc00:15:fa36:9e80:93a1, 2600:9000:2021:c200:15:fa36:9e80:93a1 Connection Reachable (25 ms)
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 222 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 222 B Sitemaps referenced 1 User-agents meta-externalagent, meta-webindexer, * Blocking No — crawling allowed
User-agent: *

Disallow: /plenty/

Allow: /plenty/api/external.php

Disallow: /xml/

Sitemap: https://www.party-schlaudt.de/sitemap.xml

User-agent: meta-externalagent

Disallow: /

User-agent: meta-webindexer

Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
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.party-schlaudt.de/
301https://party-schlaudt.de/

Preferred variant: www

HTTP → HTTPS

301http://www.party-schlaudt.de/ → https://www.party-schlaudt.de/

Consistent

A+
Domain Intelligence
party-schlaudt.de — hosted on AWS
PASS
party-schlaudt.de — hosted on AWS
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

Unknown

SSL certificate

97 days

Issued by Amazon

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

3.67.203.118

Registrar

Registrar unknown

Unlocked Name servers unknown
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Hosting
IP Address 3.67.203.118
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (0.6s)

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

Connection waterfall

DNS Lookup 80 ms TCP Connect 25 ms TLS Handshake 28 ms Server Processing 114 ms Content Transfer 38 ms
A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: LHR3-P4)
Got: x-amz-cf-id: AHDJw79raM6zXzBEyq2EDbZrUw4e5Gg5Wavdqo8QrLjPBp2ZvebKbQ==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: AHDJw79raM6zXzBEyq2EDbZrUw4e5Gg5Wavdqo8QrLjPBp2ZvebKbQ==
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 1 header(s)
Got: x-cache=Miss from cloudfront
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback