Skip to content
https://trustindex.io

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
2
PASS
6
INFO
1
Probed from Amsterdam, Netherlands
200 OK
Checks
9
6 PASS 2 REVIEW
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.trustindex.io/
200https://trustindex.io/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://trustindex.io/ → https://trustindex.io/

Consistent

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
A
DNS Records
4 A records, 15 ms lookup
PASS
4 A records, 15 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 18.239.50.120, 18.239.50.66, 18.239.50.9, 18.239.50.122
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:2078:3c00:16:1bff:6180:93a1, 2600:9000:2078:ba00:16:1bff:6180:93a1, 2600:9000:2078:9c00:16:1bff:6180:93a1, 2600:9000:2078:de00:16:1bff:6180:93a1, 2600:9000:2078:e600:16:1bff:6180:93a1, 2600:9000:2078:8e00:16:1bff:6180:93a1, 2600:9000:2078:ce00:16:1bff:6180:93a1, 2600:9000:2078:4a00:16:1bff:6180: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: dbyhivztugayu.cloudfront.net
Info::
2 nameserver(s) configured
Got: pdns1.registrar-servers.com, pdns2.registrar-servers.com
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 15 ms
Got: 15 ms
A18.239.50.120, 18.239.50.66, 18.239.50.9, 18.239.50.122
AAAA2600:9000:2078:3c00:16:1bff:6180:93a1, 2600:9000:2078:ba00:16:1bff:6180:93a1, 2600:9000:2078:9c00:16:1bff:6180:93a1, 2600:9000:2078:de00:16:1bff:6180:93a1, 2600:9000:2078:e600:16:1bff:6180:93a1, 2600:9000:2078:8e00:16:1bff:6180:93a1, 2600:9000:2078:ce00:16:1bff:6180:93a1, 2600:9000:2078:4a00:16:1bff:6180:93a1
CNAMEdbyhivztugayu.cloudfront.net
NSpdns1.registrar-servers.com, pdns2.registrar-servers.com
MX
10 mx01.inclust.com
20 mx02.inclust.com
TXT
brevo-code:6c0a00897d39c15844f87b83c18a7843
amazonses:n2QVpMe0n3XSd0hzLSrPbO0ew4zX1nlfolRbP+iQOFk=
stripe-verification=3507ac022fd083e48290294aab69af6de32a0e30b62da5478d11aab888f6...
SPF v=spf1 include:spf.ipzmarketing.com mx include:servers.mcsv.net include:spf.incl...
CAALookup not available with standard resolver
Resolved in 15 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://trustindex.io

https://trustindex.io

291 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://trustindex.io200291 msHTTP/1.1Apache/2.4.52 (Ubuntu)
A+
IPv6 Readiness
IPv6 reachable (162 ms)
PASS
IPv6 reachable (162 ms)
Info::
IPv6 is configured and reachable at 2600:9000:2078:3c00:16:1bff:6180:93a1, 2600:9000:2078:ba00:16:1bff:6180:93a1, 2600:9000:2078:9c00:16:1bff:6180:93a1, 2600:9000:2078:de00:16:1bff:6180:93a1, 2600:9000:2078:e600:16:1bff:6180:93a1, 2600:9000:2078:8e00:16:1bff:6180:93a1, 2600:9000:2078:ce00:16:1bff:6180:93a1, 2600:9000:2078:4a00:16:1bff:6180:93a1
Got: 162 ms connect
IPv6 Ready
AAAA Records 2600:9000:2078:3c00:16:1bff:6180:93a1, 2600:9000:2078:ba00:16:1bff:6180:93a1, 2600:9000:2078:9c00:16:1bff:6180:93a1, 2600:9000:2078:de00:16:1bff:6180:93a1, 2600:9000:2078:e600:16:1bff:6180:93a1, 2600:9000:2078:8e00:16:1bff:6180:93a1, 2600:9000:2078:ce00:16:1bff:6180:93a1, 2600:9000:2078:4a00:16:1bff:6180:93a1 Connection Reachable (162 ms)
A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 118 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references sitemap

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 200 OK
Size 118 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://www.trustindex.io/wp-sitemap.xml
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
HTTP Probe Timing
Total 268 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
21 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.
113 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
267 ms
Total Time Total request time from DNS lookup through full response.
269 ms

Connection waterfall

DNS Lookup 21 ms TCP Connect 1 ms TLS Handshake 113 ms Server Processing 133 ms Content Transfer 1 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: AMS58-P3)
Got: x-amz-cf-id: n4bXknkdxI-MxhjlxZh_uUARzUeGgy1OUQBBUeTVRUmB4SyguzliPQ==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: n4bXknkdxI-MxhjlxZh_uUARzUeGgy1OUQBBUeTVRUmB4SyguzliPQ==
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

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

Send Feedback