HomeDirectory Aadf.ly

adf.ly

HTTPS HTTP/2 Gzip Cloudflare Crawled in 30,685ms · June 27, 2026 14:11 UTC

adf.ly Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of adf.ly on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 14415ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 136 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 15/100 (poor). The following security headers are properly configured: X-Frame-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), 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 13 technologies across 12 categories powering adf.ly. The detected stack includes Vue.js, Bootstrap 4.0.0, Google Analytics 4, Google Tag Manager, Klarna, Zendesk, reCAPTCHA v3, Cloudflare, StackPath, Google Fonts, Vimeo, jQuery, and Font Awesome. The UI is built with Vue.js. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, adf.ly receives an overall trust score of 61/100, classified as "Likely Safe".
61
/ 100
Trust Score
15
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time14415ms
ProtocolHTTP/2
Page Size136 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Servercloudflare
Total Requests85
3rd Party Domains18
Redirect1 hop(s)
Detected Technologies (13)
⚛️ Vue.js 🎨 Bootstrap 📊 Google Analytics 4 🏷️ Google Tag Manager 💳 Klarna 🎧 Zendesk 🔒 reCAPTCHA v3 ☁️ Cloudflare ☁️ StackPath 🔤 Google Fonts 🎬 Vimeo 📦 jQuery 🎯 Font Awesome
Security Headers
Content-Security-Policy
Not set
Strict-Transport-Security (HSTS)
Not set
X-Frame-Options
Set ✓
X-Content-Type-Options
Not set
Referrer-Policy
Not set
Permissions-Policy
Not set
SSL Certificate
IssuerGoogle Trust Services
Issuer FullcountryName=US, organizationName=Google Trust Services, commonName=WE1
SubjectcommonName=adf.ly
Type
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm
Issued
Expires— (? days)
SANs

adf.ly Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, adf.ly receives a trust score of 61/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, 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, 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 adf.ly 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.
61
/ 100
Likely Safe
Trust Signals
Valid HTTPS
SPF configured
DMARC configured (p=none)
DNSSEC enabled
⚠️ Missing Content-Security-Policy
⚠️ Missing Referrer-Policy
Blacklist Checks (8/8 clean)
Google Safe Browsing clean
Phishtank clean
Urlhaus clean
Openphish clean
Dnsfilter clean
Spamhaus Dbl clean
Surbl clean
Virustotal clean

adf.ly Technology Stack & Detected Technologies

🤖 AI Summary
Our technology detection engine scanned adf.ly and identified 13 distinct technologies across 12 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. UI Library: Vue.js — handles the user interface rendering and component management for adf.ly. CSS Framework: Bootstrap (version 4.0.0) — provides the styling and responsive layout system for adf.ly. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for adf.ly. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for adf.ly. Payments: Klarna — processes payment transactions for adf.ly. Support: Zendesk — handles customer support tickets and knowledge bases for adf.ly. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for adf.ly. CDN: Cloudflare and StackPath — accelerates content delivery by caching assets at edge locations worldwide for adf.ly. Fonts: Google Fonts — delivers web fonts for typography for adf.ly. Video: Vimeo — provides video hosting and playback for adf.ly. JavaScript Library: jQuery — provides utility functions and DOM manipulation for adf.ly. Icon Set: Font Awesome — provides additional functionality for adf.ly. We also extracted the following tracking identifiers: Google Tag Manager container GTM-TZ69NZG. These IDs can be used to identify other websites operated by the same organization.
UI Library
⚛️ Vue.js(95%)
CSS Framework
🎨 Bootstrap 4.0.0(100%)
Analytics
📊 Google Analytics 4(95%)
Tag Manager
🏷️ Google Tag Manager(95%)
Payments
💳 Klarna(95%)
Support
🎧 Zendesk(95%)
Security
🔒 reCAPTCHA v3(95%)
CDN
☁️ Cloudflare(100%)☁️ StackPath(95%)
Fonts
🔤 Google Fonts(95%)
Video
🎬 Vimeo(95%)
JavaScript Library
📦 jQuery(95%)
Icon Set
🎯 Font Awesome(95%)
Tracking IDs
gtm_idGTM-TZ69NZG

adf.ly Performance, Speed & Core Web Vitals

🤖 AI Summary
adf.ly delivers its homepage in 14415ms (server response time), which is considered slow by industry standards. The total page weight is 136 KB, and we detected 85 resource requests loading assets from 18 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: 4 out of 11 CSS files and 12 out of 22 JavaScript files are minified. Minifying the remaining 17 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 adf.ly produces approximately 0.07g 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 136 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for adf.ly. 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.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.07g
RatingA
Page Weight & Optimization
HTML Size136 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests85
3rd Party Domains18
CSS Minified4/11
JS Minified12/22

adf.ly DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
adf.ly resolves to the IPv4 address 172.66.43.117, but does not support IPv6. IPv6 adoption is increasingly important as IPv4 address space becomes exhausted, and some ISPs and regions are transitioning to IPv6-only connectivity. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: jim.ns.cloudflare.com and zara.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 adf.ly is handled by cloudflare.net with 3 MX records configured: route3.mx.cloudflare.net, route1.mx.cloudflare.net, and route2.mx.cloudflare.net. 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 was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is enabled for adf.ly, 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 6 active subdomains for adf.ly: api.adf.ly, cdn.adf.ly, mail.adf.ly, static.adf.ly, support.adf.ly, and www.adf.ly. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
172.66.43.117
172.66.40.139
NS
jim.ns.cloudflare.com
zara.ns.cloudflare.com
MX
route3.mx.cloudflare.net
route1.mx.cloudflare.net
route2.mx.cloudflare.net
Email & Authentication
SPF
DMARC p=none
DKIM
DNSSEC
MX Providercloudflare.net
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportNo
Subdomains (6 found)
api.adf.ly cdn.adf.ly mail.adf.ly static.adf.ly support.adf.ly www.adf.ly

adf.ly Page Content, Images & Accessibility

🤖 AI Summary
The homepage of adf.ly contains 9,402 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 9 H2 headings, 5 H3 headings, 20 H4 headings, 2 H5, and 0 H6 headings. The page includes 8 images. 8 images (100%) 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 0% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 20 internal links pointing to other pages on the same domain and 18 external links pointing to third-party websites. There are 22 external JavaScript files, 11 CSS stylesheets, and 3 iframes on the page. The site implements the following web standards and features: Progressive Web App (PWA) manifest (enabling app-like installation). 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 adf.ly: Visa, Mastercard, American Express, Discover, Apple Pay, Google Pay, and Klarna. 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 2 platforms: Twitter (@Linkvertise) and Youtube (@UCCq5_toZNT2QYNmHjHXrHbg). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
9,402
Words
8
Images
0%
Alt Text Score
136
Page Size (KB)
Content Structure
H1Highest payout rates
H2 Tags9
H3 Tags5
H4 Tags20
H5 Tags2
H6 Tags0
Internal Links20
External Links18
Assets & Features
JavaScript Files22
JS Minified12/22
CSS Files11
CSS Minified4/11
Iframes3
Images8
Missing Alt8
SitemapNo
Robots.txtNo
PWAYes ✓
AMPNo
RSS FeedNo
Payment Methods Detected
💳 Visa💳 Mastercard💳 American Express💳 Discover💳 Apple Pay💳 Google Pay💳 Klarna
Social Media Presence
Twitter: @LinkvertiseYoutube: @UCCq5_toZNT2QYNmHjHXrHbg

adf.ly SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for adf.ly is good at 61 characters: "Linkvertise - Earn Money with Posts | Monetization done right". The length is acceptable, though it may be slightly truncated in some search result displays. No meta description is configured for adf.ly. 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://publisher.linkvertise.com, preventing duplicate content issues, the page language is declared as de, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to adf.ly 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.
Google SERP Preview
Linkvertise - Earn Money with Posts | Monetization done right
https://adf.ly
Meta Tags
TitleLinkvertise - Earn Money with Posts | Monetization done righ...
Title Length61 chars
Meta Desc Length0 chars
H1Highest payout rates
Languagede
Canonicalhttps://publisher.linkvertise.com
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema Types
OG Type
OG ImageNot set
Twitter Card
FaviconSet ✓