Skip to content
https://truffa.net

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
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.
C
Reverse DNS
Action
0/6 IPs match cert SAN
REVIEW
0/6 IPs match cert SAN
Info::
PTR lookup failed for 104.26.13.238: lookup 104.26.13.238: 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 172.67.69.95: lookup 172.67.69.95: 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 104.26.12.238: lookup 104.26.12.238: 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 2606:4700:20::681a:cee: lookup 2606:4700:20::681a:cee: 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 2606:4700:20::681a:dee: lookup 2606:4700:20::681a:dee: 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 2606:4700:20::ac43:455f: lookup 2606:4700:20::ac43:455f: 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
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 301-redirects to HTTPS

www / non-www

200https://www.truffa.net/
200https://truffa.net/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://truffa.net/ https://www.truffa.net/

Consistent

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

Certificate validity

73
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
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
3 A records, 27 ms lookup
PASS
3 A records, 27 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.13.238, 172.67.69.95, 104.26.12.238
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::681a:cee, 2606:4700:20::681a:dee, 2606:4700:20::ac43:455f
Info::
2 nameserver(s) configured
Got: leonard.ns.cloudflare.com, treasure.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
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: 27 ms
Got: 27 ms
A104.26.13.238, 172.67.69.95, 104.26.12.238
AAAA2606:4700:20::681a:cee, 2606:4700:20::681a:dee, 2606:4700:20::ac43:455f
CNAME
NSleonard.ns.cloudflare.com, treasure.ns.cloudflare.com
MX
10 mail.truffa.net
TXT
CAALookup not available with standard resolver
Resolved in 27 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
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 7ms across 3 resolvers (spread 9ms)
PASS
Mean 7ms across 3 resolvers (spread 9ms)
Info::
Quad9: 4ms
Got: 4ms via 9.9.9.9:53
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Google: 13ms
Got: 13ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 235 ms total
PASS
1 redirect(s), 235 ms total
Info::
Single redirect
Got: https://truffa.net → https://www.truffa.net/ (301)
Info::
WWW normalization redirect

https://truffa.net

130 ms · HTTP/1.1

301

https://www.truffa.net/

105 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://truffa.net301130 msHTTP/1.1cloudflare
2https://www.truffa.net/200105 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::681a:cee, 2606:4700:20::681a:dee, 2606:4700:20::ac43:455f
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::681a:cee, 2606:4700:20::681a:dee, 2606:4700:20::ac43:455f Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 5 URLs
PASS
robots.txt present, sitemap with 5 URLs
Info::
robots.txt is present
Got: 636 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 5 entries
Info::
Sitemap index with 5 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 636 B Sitemaps referenced 1 User-agents *, Mediapartners-Google, Adsbot-Google, Googlebot-Image, Googlebot-Mobile, ia_archiver Blocking No — crawling allowed
User-agent: *
Disallow: /comments/feed
Disallow: /feed/$
Disallow: /*/feed/$
Disallow: /*/feed/rss/$
Disallow: /*/trackback/$
Disallow: /*/*/feed/$
Disallow: /*/*/feed/rss/$
Disallow: /*/*/trackback/$
Disallow: /*/*/*/feed/$
Disallow: /*/*/*/feed/rss/$
Disallow: /*/*/*/trackback/$
Disallow: /trackback/
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /*.inc$
Disallow: */trackback/

User-agent: Mediapartners-Google
Allow: /

User-agent: Adsbot-Google
Allow: /

User-agent: Googlebot-Image
Allow: /

User-agent: Googlebot-Mobile
Allow: /

User-agent: ia_archiver
Disallow: /

Sitemap: https://www.truffa.net/sitemap.xml

A+
Domain Intelligence
truffa.net — via RegistryGate GmbH, 18 years, 11 months old
PASS
truffa.net — via RegistryGate GmbH, 18 years, 11 months old
Info::
Domain registered until Nov 26, 2026 (3 months remaining)
Info::
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.
Info::
Registrar: RegistryGate GmbH
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.
Domain expiry

109 days

November 26, 2026

SSL certificate

73 days

Issued by Let's Encrypt

Domain age

18 years, 11 months

Registered November 26, 2007

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::681a:dee

Registrar

RegistryGate GmbH

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 RegistryGate GmbH
Created November 26, 2007 (18 years, 11 months ago)
Expires November 26, 2026 (3 months)
Last Updated August 4, 2026
Name Servers leonard.ns.cloudflare.com, treasure.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:20::681a:dee
Data source: rdap (0.0s)

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

Connection waterfall

DNS Lookup 10 ms TCP Connect 1 ms TLS Handshake 13 ms Server Processing 120 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: AMS)
Got: cf-ray: a26ecd0a0f405925-AMS
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a26ecd0a0f405925-AMS
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback