tpt.org

We performed a comprehensive analysis of tpt.org on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 15562ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 7283 KB, and the site is served behind a CDN (Content Delivery Network). The website uses a secure HTTPS connection with a valid SSL certificate issued by Google Trust Services (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and ECDSA-SHA256 signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-08-03, which is 34 days from now. The security headers analysis reveals a score of 20/100 (poor). The following security headers are properly configured: Strict-Transport-Security (HSTS). However, the site is missing Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 11 technologies across 8 categories powering tpt.org. The detected stack includes Squarespace, Drupal, Next.js chunks, React, Vite, Google Analytics 4, Google Tag Manager, LinkedIn Insight Tag, Google AdSense, Vimeo, and YouTube Embed. The site uses Next.js as its primary framework (version chunks). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, tpt.org receives an overall trust score of 72/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, tpt.org receives a trust score of 72/100, which places it in the "Likely Safe" category. This score is calculated by evaluating multiple factors including SSL certificate validity, domain registration history, email authentication protocols, security header configuration, and blacklist status across major threat intelligence databases. The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, a valid SSL certificate issued by Google Trust Services with 34 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a reject policy — the strongest available setting. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), missing Referrer-Policy, potentially leaking URL information to third parties, the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity, and DNSSEC is not enabled, leaving DNS queries vulnerable to spoofing attacks. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked tpt.org against 8 major blacklist databases including Google Safe Browsing, Phishtank, Urlhaus, Openphish, Dnsfilter, Spamhaus Dbl, Surbl, and Virustotal. The domain passed all 8 checks with a clean status, meaning it has not been flagged for phishing, malware distribution, spam, or other malicious activities by any of the tested threat intelligence providers.

Our technology detection engine scanned tpt.org and identified 11 distinct technologies across 8 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CMS: Squarespace and Drupal — manages the content and page structure for tpt.org. Framework: Next.js (version chunks) — provides the application framework and routing for tpt.org. UI Library: React — handles the user interface rendering and component management for tpt.org. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for tpt.org. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for tpt.org. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for tpt.org. Advertising: LinkedIn Insight Tag and Google AdSense — handles advertising pixel tracking and conversion measurement for tpt.org. Video: Vimeo and YouTube Embed — provides video hosting and playback for tpt.org. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-6EFN2GM1EK and Google Tag Manager container GTM-KS2XXVHP. These IDs can be used to identify other websites operated by the same organization.

tpt.org delivers its homepage in 15562ms (server response time), which is considered slow by industry standards. The total page weight is 7283 KB, and we detected 34 resource requests loading assets from 4 third-party domains. A high number of third-party domains can significantly impact page load time due to additional DNS lookups and TLS handshakes required for each domain. The website uses Gzip compression for text-based assets, achieving an estimated 60.0% reduction in transfer size. This reduces bandwidth usage and improves page load times, especially for visitors on slower connections. Asset minification status: 0 out of 4 CSS files and 0 out of 18 JavaScript files are minified. Minifying the remaining 22 unminified file(s) could further reduce page weight by 10-30% for those assets. Minification is a best practice that reduces download sizes without affecting functionality. The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors. From an environmental perspective, each page view of tpt.org produces approximately 3.56g of CO₂, earning a carbon rating of F. The website's carbon footprint could be reduced by optimizing images, enabling compression, reducing third-party scripts, and leveraging caching. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 7283 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for tpt.org. This typically means the site doesn't have enough real-world Chrome user traffic to generate statistically significant field data, or the domain is not included in the CrUX dataset. Core Web Vitals (LCP, INP, CLS) are important Google ranking factors that measure real user experience.

tpt.org resolves to the IPv4 address 104.20.46.120 and also supports IPv6 (2606:4700:10::ac42:922a), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: dell.ns.cloudflare.com and owen.ns.cloudflare.com. Having 2 name servers provides good redundancy — if one fails, the others can continue serving DNS queries. The choice of name servers often indicates the DNS hosting provider or CDN service being used. Email for tpt.org is handled by Microsoft 365 with 1 MX records configured: tpt-org.mail.protection.outlook.com. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF (Sender Policy Framework) is configured, which specifies which mail servers are authorized to send email on behalf of this domain. This helps prevent email spoofing and improves email deliverability. DMARC (Domain-based Message Authentication, Reporting and Conformance) is configured with a reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is not enabled for tpt.org. While not critical for most websites, DNSSEC adds an important security layer by ensuring DNS responses haven't been tampered with during transit. Enabling DNSSEC is recommended for domains handling sensitive data or financial transactions.

The homepage of tpt.org contains 10 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The link structure consists of 2 internal links pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 18 external JavaScript files, 4 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior). Notable missing features: XML Sitemap and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on tpt.org: American Express, Discover, and Affirm. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates. The website has social media presence across 4 platforms: Instagram (@twincitiespbs\), Linkedin (@twin-cities-pbs), Youtube (@SkillsvilleOfficial\), and Tiktok (@twincitiespbs\). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for tpt.org is good at 27 characters: "Twin Cities PBS – Watch Now". The length is acceptable, though it may be slightly truncated in some search result displays. No meta description is configured for tpt.org. This is a critical SEO oversight — without a meta description, Google will auto-generate a snippet from page content, which may not accurately represent the page or entice users to click. Adding a unique, compelling meta description of 120-155 characters is strongly recommended. The page language is declared as en and a favicon is configured. Open Graph meta tags are configured with 2/4 recommended fields: OG title ("Twin Cities PBS – Watch Now..."), OG image (social sharing thumbnail), These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol. A Twitter Card of type summary_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" type displays a large image preview, which typically generates higher engagement rates than the basic card type.