ftd.travel

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, ftd.travel receives a trust score of 63/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, DKIM (DomainKeys Identified Mail) providing cryptographic email verification, and DNSSEC providing authenticated DNS responses. 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, and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked ftd.travel 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.

🤖 AI Summary

Our technology detection engine scanned ftd.travel 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. CSS Framework: Bootstrap — provides the styling and responsive layout system for ftd.travel. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for ftd.travel. Fonts: Google Fonts — delivers web fonts for typography for ftd.travel. JavaScript Library: jQuery (version 1.11.1.) — provides utility functions and DOM manipulation for ftd.travel. Icon Set: Font Awesome — provides additional functionality for ftd.travel. Performance: WP Rocket — optimizes page loading speed and performance for ftd.travel.

🤖 AI Summary

ftd.travel delivers its homepage in 53544ms (server response time), which is considered slow by industry standards. The total page weight is 25 KB, and we detected 96 resource requests loading assets from 8 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: 2 out of 11 CSS files and 3 out of 6 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 ftd.travel produces approximately 0.01g 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 25 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for ftd.travel. 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.

🤖 AI Summary

ftd.travel resolves to the IPv4 address 104.21.58.233 and also supports IPv6 (2606:4700:3032::6815:3ae9), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: lorna.ns.cloudflare.com and yahir.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 ftd.travel is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 more. 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 none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. DKIM (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit. DNSSEC is enabled for ftd.travel, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites. Our subdomain enumeration scan discovered 25 active subdomains for ftd.travel: admin.ftd.travel, api.ftd.travel, app.ftd.travel, apps.ftd.travel, blog.ftd.travel, cdn.ftd.travel, community.ftd.travel, and dev.ftd.travel. Plus 17 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of ftd.travel contains 103 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 2 H2 headings, 0 H3 headings, 1 H4 headings. The page includes 6 images. 2 images (33%) 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 67% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 22 internal links pointing to other pages on the same domain and 1 external link pointing to third-party websites. There are 6 external JavaScript files, 11 CSS stylesheets, and 0 iframes on the page. Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on ftd.travel: Visa. 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: Facebook (@ftdtravel), Twitter (@ftdtravel), Instagram (@ftdtravel), and Youtube (@UCn2kH_xLaBFmM-tDXBY3r5g). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

🤖 AI Summary

The title tag for ftd.travel is too long at 72 characters: "Partner / Travel Agent Login for B2B Flights & Bus Bookings - FTD Travel". At 72 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning. The meta description is 106 characters (well-optimized): "Travel Agents Login into their account for the best B2B prices for Flights & Bus Bookings with FTD Travel.". Google typically displays up to 155-160 characters of the meta description in search results. A compelling meta description with a clear call-to-action can significantly improve click-through rates from search results. The page language is declared as en. No Open Graph tags are configured. When someone shares a link to ftd.travel on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing.

🤖 AI Summary

Related domain discovery works by finding other websites that share the same IP address, Google Tag Manager container ID, Google Analytics property, or advertising pixel IDs with ftd.travel. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. No tracking IDs were detected on this page that could be used for cross-domain matching.