Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations294 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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
ADNS Records2 A records, 255 ms lookupPASS
| A | 76.223.6.18, 13.248.129.228 |
| AAAA | — |
| CNAME | — |
| NS | ns2.xmission.com, ns.xmission.com, ns1.xmission.com, ns3.xmission.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | mail.sltrib.com. SPF v=spf1 ip4:13.110.6.208/28 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.8... yahoo-verification-key=4tG7Hfbd+ymfRk5acPjcu/WlLdeWb0WBMHQwDLd+wsI= Validity-Domain-Verification=Z+STTbvvLcYaP5dj4JDDL5AXzv4= google-site-verification=nHYZSFG8tf-3BK_yykBHNynESO_y_IUFlHkocdGxBtg |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
ARedirect Chain1 redirect(s), 340 ms totalPASS
https://sltrib.com
182 ms · HTTP/1.1
https://www.sltrib.com:443/
158 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://sltrib.com | 301 | 182 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.sltrib.com:443/ | 200 | 158 ms | HTTP/1.1 | openresty |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 43 URLsPASS
Sitemap: https://www.sltrib.com/arc/outboundfeeds/sitemap/?outputType=xml
User-agent: *
Disallow: /pb/
User-agent: Google-Extended
Disallow: /
User-agent: PerplexityBot
Disallow: /
User-agent: YouBot
Disallow: /
User-agent: FacebookBot
Allow: /
User-agent: facebookexternalhit
Allow: /
User-agent: facebookcatalog
Allow: /
User-agent: Twitterbot
Allow: /
User-agent: LinkedInBot
Allow: /
User-agent: BufferLinkPreviewBot
Allow: /
# add 3/11/2026
User-agent: GPTBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: Claude-Web
Disallow: /
User-agent: CCBot
Disallow: /
# outbound 3/11/2026
- https://www.sltrib.com/opinion/letters/2026/04/21/letter-utahs-dual-language/
- https://www.sltrib.com/resizer/v2/45SEZK64GJDGRI3UYKB5SEZEFM.jpg?auth=f87f434ee1400a6be5118410161e809cb758400853745a7ded78ec75f297d771&smart=true&width=2900&height=1987
- https://www.sltrib.com/opinion/letters/2026/04/21/letter-communities-nationwide-are/
- https://www.sltrib.com/resizer/v2/FHIDJYOIRZAMXJIMQFJAUXOWLE.jpg?auth=857dec0eee8a4534237ae2cf7536f0b7614ef96ed1313e4b600b3755c04fe665&smart=true&width=4000&height=2667
- https://www.sltrib.com/news/politics/2026/04/17/utahs-us-rep-celeste-maloy-has/
A+Domain Intelligencesltrib.com — via Network Solutions, LLC, 32 years, 7 months old, hosted on AWSPASS
1722 days
March 2, 2031
294 days
Issued by Amazon
32 years, 7 months
Registered March 1, 1994
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
13.248.129.228
Network Solutions, LLC
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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