mttf.org

We performed a comprehensive analysis of mttf.org on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 29202ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 96 KB, and the site is served behind a CDN (Content Delivery Network). Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted. The security headers analysis reveals a score of 0/100 (poor). No security headers are configured, which is a significant security concern. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), 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 6 technologies across 6 categories powering mttf.org. The detected stack includes WordPress 7.0, Google Analytics 4, Cloudflare, Google Fonts, jQuery, and WP Rocket. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, mttf.org receives an overall trust score of 59/100, classified as "Caution Advised".

After conducting a thorough safety and legitimacy analysis, mttf.org receives a trust score of 59/100, which places it in the "Caution Advised" 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, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a quarantine policy. 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 mttf.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 mttf.org and identified 6 distinct technologies across 6 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CMS: WordPress (version 7.0) — manages the content and page structure for mttf.org. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for mttf.org. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for mttf.org. Fonts: Google Fonts — delivers web fonts for typography for mttf.org. JavaScript Library: jQuery — provides utility functions and DOM manipulation for mttf.org. Performance: WP Rocket — optimizes page loading speed and performance for mttf.org. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-ERMGZFGTZD. These IDs can be used to identify other websites operated by the same organization.

mttf.org delivers its homepage in 29202ms (server response time), which is considered slow by industry standards. The total page weight is 96 KB, and we detected 95 resource requests loading assets from 7 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: 1 out of 4 CSS files and 9 out of 18 JavaScript files are minified. Minifying the remaining 12 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 mttf.org produces approximately 0.05g of CO₂, earning a carbon rating of A. This places the website among the cleanest on the web, demonstrating efficient use of server resources and optimized content delivery. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 96 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for mttf.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.

mttf.org resolves to the IPv4 address 172.67.73.67 and also supports IPv6 (2606:4700:20::ac43:4943), demonstrating modern network infrastructure readiness. The domain has 3 A record(s) configured. The domain name system is managed by 2 name servers: gwen.ns.cloudflare.com and simon.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 mttf.org is handled by Microsoft 365 with 1 MX records configured: mttf-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 quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. 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 mttf.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. Our subdomain enumeration scan discovered 25 active subdomains for mttf.org: admin.mttf.org, api.mttf.org, app.mttf.org, apps.mttf.org, blog.mttf.org, cdn.mttf.org, community.mttf.org, and dev.mttf.org. Plus 17 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of mttf.org contains 390 words of visible text content. This is a moderate amount of content. The page is structured with 1 H2 headings, 5 H3 headings, 0 H4 headings. The page includes 14 images. 12 images (86%) are missing alt text attributes, which is a significant concern for both accessibility and SEO. Screen readers rely on alt text to describe images to visually impaired users, and search engines use alt text to understand image content. Only 14% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 40 internal links pointing to other pages on the same domain and 5 external links pointing to third-party websites. There are 18 external JavaScript files, 4 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages), Schema.org structured data (BreadcrumbList, EntryPoint, ListItem, PropertyValueSpecification, ReadAction, SearchAction, WebPage, and WebSite), and RSS feed for content syndication. Notable missing features: robots.txt. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for mttf.org is well-optimized at 59 characters: "Mason Tenders’ Training Fund - Mason Tenders' Training Fund". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. No meta description is configured for mttf.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 canonical url is correctly set to https://www.mttf.org/, preventing duplicate content issues, the page language is declared as en-us, the meta robots directive is set to index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Mason Tenders' Training Fund..."), OG description, OG image (social sharing thumbnail), OG type (website). 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. The site implements Schema.org structured data with the following types: BreadcrumbList, EntryPoint, ListItem, PropertyValueSpecification, ReadAction, SearchAction, WebPage, and WebSite. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates.