WebTrackly
Domain Intelligence

Mastering DNS Records for HTTPS Detection: Uncover Secure Domains, Identify Market Trends, and Generate High-Value Leads

blureshot April 17, 2026 44 min read 116 views
dns record https - Mastering DNS Records for HTTPS Detection: Uncover Secure Domains, Identify Market Trends, and Generate High-Value Leads
dns record https - Mastering DNS Records for HTTPS Detection: Uncover Secure Domains, Identify Market Trends, and Generate High-Value Leads

Your sales team is missing out on 40% of its potential pipeline because you're not efficiently identifying and segmenting secure domains. In a world where 95% of websites now use HTTPS, failing to accurately track and leverage this crucial security indicator means your competitive intelligence is incomplete, your lead generation is inefficient, and your market analysis is fundamentally flawed. Modern web intelligence demands a granular understanding of the underlying infrastructure, and that starts with dissecting DNS records to reveal not just if a site is secure, but how it's secured and what that implies for your business strategy.

TL;DR / Key Takeaways

  • DNS records are the bedrock of web infrastructure, directing traffic and providing critical insights into a domain's hosting, email, and security configurations, including how it supports HTTPS.
  • HTTPS adoption is near-universal (95%+), making it a baseline for trust and a key filter for identifying professional, active businesses.
  • Specific DNS records like CAA, DANE (TLSA), and SVCB/HTTPS directly inform certificate issuance policies and secure connection parameters, offering deep insights into a domain's security posture.
  • WebTrackly automates the complex process of parsing billions of DNS records and combining this with live HTTPS detection, allowing you to filter 200M+ domains by security status, certificate authority, and underlying infrastructure.
  • Leverage this data for hyper-targeted lead generation, competitive analysis, market trend identification, and cybersecurity research, uncovering opportunities missed by traditional tools.
  • Avoid common pitfalls like relying solely on HTTP status or ignoring advanced security DNS records; integrate comprehensive domain intelligence for accurate, actionable insights.
  • WebTrackly offers unparalleled scale, accuracy, and depth, providing a significant ROI for B2B sales, marketing, and data teams by transforming raw web data into tangible business value.

Table of Contents


The Indispensable Role of DNS Records in a Secure Web

The internet runs on a foundation of trust and connectivity, and at its core lies the Domain Name System (DNS). While often seen as a mere "phonebook" for the internet, DNS records are far more than simple address pointers. They are the digital breadcrumbs that reveal a domain's entire infrastructure, from its hosting provider to its email routing, and increasingly, its security posture concerning HTTPS. Understanding the interplay between dns record https is no longer a niche technical concern; it's a strategic imperative for anyone looking to generate leads, conduct competitive intelligence, or simply understand the modern web at scale.

Understanding DNS: The Internet's Phonebook

Every time you type a domain like webtrackly.com into your browser, DNS springs into action. It translates that human-readable name into an IP address (e.g., 104.26.1.189), which is a numerical address computers use to locate each other. This translation is managed by a hierarchy of DNS servers that store various types of records.

Here's a quick rundown of essential DNS record types and their foundational role:

  • A Record (Address Record): Maps a domain name to an IPv4 address. This is the most fundamental record, telling browsers where to find the website's server.
  • AAAA Record (IPv6 Address Record): Maps a domain name to an IPv6 address. As IPv6 adoption grows, this record becomes increasingly important.
  • CNAME Record (Canonical Name Record): Aliases one domain name to another. For example, www.example.com might be a CNAME for example.com.
  • MX Record (Mail Exchange Record): Specifies the mail servers responsible for accepting email messages on behalf of a domain. Critical for identifying a domain's email infrastructure.
  • TXT Record (Text Record): Stores arbitrary text strings. Often used for SPF (Sender Policy Framework) records to combat email spoofing, DKIM (DomainKeys Identified Mail) for email authentication, and domain verification.
  • NS Record (Name Server Record): Specifies the authoritative DNS servers for a domain, delegating responsibility to specific servers.
  • SRV Record (Service Record): Specifies the location (hostname and port number) of servers for specified services. Less common for general web browsing but important for specific applications.

These records collectively paint a picture of a domain's underlying infrastructure. For instance, knowing a domain's A record reveals its server's IP, which can then be cross-referenced with IP geolocation databases and hosting provider information.

Beyond the Basics: DNS Records and HTTPS

While traditional DNS records (A, CNAME) don't directly state "this domain uses HTTPS," they provide the crucial pointers to the server that does implement HTTPS. When a browser requests https://webtrackly.com, the DNS system first resolves webtrackly.com to its IP address. Then, the browser connects to that IP address on port 443 (the standard port for HTTPS) and initiates the TLS handshake, verifying the SSL/TLS certificate.

However, the connection between dns record https goes deeper with newer, security-focused DNS record types:

  • CAA Record (Certificate Authority Authorization): This record type allows a domain owner to specify which Certificate Authorities (CAs) are authorized to issue SSL/TLS certificates for their domain. If a CA that is not listed attempts to issue a certificate, it should be rejected. This is a powerful mechanism to prevent mis-issuance and enhance security. Detecting CAA records can reveal a company's preferred CA and its commitment to certificate management.
  • DANE (DNS-based Authentication of Named Entities) / TLSA Record: DANE allows domain owners to publish their SSL/TLS certificate fingerprints or public keys directly in DNS using TLSA records. This provides an additional layer of trust, allowing clients to verify that the certificate presented by a server matches the one published in DNS, without relying solely on a hierarchy of CAs. While DANE adoption is still growing, its presence signifies a high level of security sophistication.
  • SVCB (Service Binding) and HTTPS Records (RFC 9460): These are the most direct dns record https connections. Introduced to improve performance and security, SVCB and HTTPS records allow a domain to declare its support for HTTPS, specify alternative endpoints, and even indicate preferred connection parameters (like HTTP/3 support) directly within DNS. This enables clients to establish secure, optimized connections with fewer round trips, reducing latency and enhancing privacy. Detecting these records indicates a domain is at the forefront of web performance and security best practices.

By analyzing these specific DNS records, WebTrackly can go beyond a simple "HTTPS yes/no" and provide nuanced insights into a domain's security strategy and infrastructure choices. This level of detail is invaluable for targeted outreach, competitive analysis, and cybersecurity assessments.

The Rise of HTTPS and Its Implications

The shift to HTTPS has been monumental. In 2016, only about 40% of page loads were encrypted. Today, that figure stands at over 95% globally. Google's push for "HTTPS Everywhere," browser warnings for non-secure sites, and the availability of free certificates (like Let's Encrypt) have driven this rapid adoption.

Why this matters for you:

  • Trust and Credibility: Users inherently trust secure sites more. For B2B sales, a prospect with HTTPS indicates a professional, reputable business.
  • SEO Advantage: Google openly favors HTTPS sites, giving them a slight ranking boost. SEO specialists must prioritize secure domains.
  • Data Privacy & Security: HTTPS encrypts data in transit, protecting sensitive information like login credentials and payment details. This is non-negotiable for e-commerce, financial services, and any site handling personal data.
  • Technology Adoption Indicator: The presence of HTTPS, especially with advanced DNS security records, can signal a company's general tech savviness and willingness to invest in modern infrastructure.

A domain without HTTPS in 2024 is often a red flag, indicating neglect, outdated technology, or a non-serious operation. Conversely, a domain with robust HTTPS and advanced DNS security records presents a high-value target.

Manual vs. Automated DNS and HTTPS Detection

Imagine trying to manually gather this data for thousands or even millions of domains.

  • Manual Approach:

    • Using dig or nslookup for DNS records: dig webtrackly.com A, dig webtrackly.com CAA, dig webtrackly.com TLSA. This is tedious and slow for a single domain, let alone a large list.
    • Checking HTTPS status: Visiting each site, inspecting the browser's padlock icon, or using curl -I https://example.com.
    • Analyzing certificates: Manually inspecting certificate details (issuer, expiration, chain) in the browser dev tools.
    • Limitations: Extremely time-consuming, prone to human error, impossible to scale, provides only a snapshot. A single person might process 50 domains in an hour, but what about 50,000?
  • Automated Approach (WebTrackly):

    • WebTrackly's infrastructure continuously scans and indexes over 200 million domains.
    • It performs comprehensive DNS lookups, capturing A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, DANE (TLSA), and SVCB/HTTPS records.
    • Simultaneously, it performs live HTTP/HTTPS checks, identifies the certificate issuer, validity, and associated technologies.
    • This data is then enriched with technology detection, hosting information, geographic location, and business contact details.
    • Advantages: Unprecedented scale, consistent accuracy, real-time updates, granular filtering, API access for integration, and a unified view of domain intelligence.

Real-world Scenario: A B2B SaaS company selling a security monitoring tool needs to target enterprise-level prospects. They know that companies investing in advanced security often implement DANE or CAA records. Manually identifying these companies is a non-starter. With WebTrackly, they can filter their entire target market by the presence of these specific dns record https types, instantly generating a list of highly qualified leads that are demonstrably security-conscious. This moves them from broad, untargeted outreach to surgically precise engagement.

Ready to find your next 10,000 leads?
WebTrackly's domain intelligence platform lets you search 200M+ domains by technology, hosting, country, and contacts.
Start Free → | View Pricing →

Profit from Precision: Advanced Use Cases for DNS and HTTPS Data

The ability to filter and analyze domains based on their DNS records and HTTPS status is a game-changer across multiple industries. It transforms generic lists into hyper-targeted opportunities. Here are 5 specific, detailed use cases demonstrating how to profit from this data using WebTrackly.

1. For SaaS Sales: Targeting Secure E-commerce Platforms with Specific Hosting

  • Target Audience: Sales Development Representatives (SDRs) and Account Executives (AEs) selling payment gateway solutions, e-commerce security tools, or performance optimization services.
  • Problem: Identifying high-value e-commerce prospects that are actively maintaining secure, modern infrastructure, often tied to specific hosting environments known for scalability and reliability. Generic lists of "e-commerce sites" yield low conversion rates due to varying tech stacks and security postures.
  • Solution with WebTrackly:
    1. Filter by CMS: Start by filtering WebTrackly's 200M+ domains for e-commerce platforms like Shopify, Magento, WooCommerce, or BigCommerce.
    2. Filter by HTTPS Status: Add a filter for has_https: true to ensure all results are using secure connections. This immediately removes outdated or non-serious stores.
    3. Refine by Hosting Provider & DNS Records: Further narrow down by hosting providers known for enterprise-grade solutions (e.g., AWS, Google Cloud, DigitalOcean, Cloudflare) and look for the presence of specific dns record https types like CAA or SVCB/HTTPS records. This indicates a sophisticated, security-conscious operation.
    4. Extract Contacts: Utilize WebTrackly's business contact extraction to get verified emails and phone numbers for decision-makers (e.g., CTOs, E-commerce Managers).
    5. Export & Integrate: Export the refined list as CSV and import directly into Salesforce or HubSpot, enriching existing lead records with detailed technology and security insights.
  • Expected Results:
    • 30% increase in lead quality: Focusing on secure, well-managed e-commerce sites means a higher likelihood of budget and need for advanced solutions.
    • 2x faster sales cycle: SDRs spend less time qualifying, as the data pre-qualifies prospects based on their tech stack and security commitment.
    • Higher conversion rates: Personalized outreach messages tailored to their specific e-commerce platform, hosting, and security features resonate more powerfully. For example, "We noticed you're running Shopify on AWS with advanced CAA records – our payment gateway integrates seamlessly to enhance your existing security posture..."

2. For Digital Marketing Agencies: Competitive Analysis of Secure Backlink Profiles

  • Target Audience: SEO specialists, content strategists, and link-building teams at digital marketing agencies.
  • Problem: Understanding competitors' backlink strategies, especially identifying high-authority, secure domains linking to them. Many backlink analysis tools don't provide deep insights into the infrastructure of linking domains, such as their hosting, CMS, or security records, making it hard to replicate or improve upon.
  • Solution with WebTrackly:
    1. Identify Competitors: Use standard SEO tools (Ahrefs, SEMrush) to get a list of domains linking to your top competitors.
    2. Bulk Upload to WebTrackly: Upload this list of competitor backlinks into WebTrackly for comprehensive profiling.
    3. Filter for Authority & Security: Filter these domains by has_https: true, specific CMS (e.g., WordPress for blogs, Drupal for enterprise), and high-value hosting providers. Crucially, identify domains with advanced dns record https like DANE (TLSA) records, signaling very high security standards and therefore higher authority.
    4. Analyze Technology Stack: Identify common technologies (e.g., specific analytics tools, marketing automation platforms) on these high-authority, secure linking domains.
    5. Extract Contacts for Outreach: Use WebTrackly to find contact information for these domains, targeting content managers or webmasters.
  • Expected Results:
    • Identification of 200-500 high-authority, secure backlink opportunities per competitor that are often overlooked.
    • Improved outreach success rates by 15-20% due to highly qualified targets and deeper understanding of their tech stack, allowing for more personalized pitches.
    • Strategic insights into competitor link-building patterns, revealing preferred security configurations or hosting environments among their most valuable links. This allows the agency to target similar profiles.

3. For Cybersecurity Researchers: Identifying Domains with Advanced DNS Security Implementations

  • Target Audience: Cybersecurity analysts, threat intelligence teams, and security product developers.
  • Problem: Mapping the adoption and configuration of advanced DNS security standards (like DANE/TLSA, CAA, DNSSEC) across specific industries or geographic regions. This is critical for understanding the threat landscape, identifying potential vulnerabilities, or assessing the security posture of a supply chain. Manual checks are impossible at scale.
  • Solution with WebTrackly:
    1. Define Scope: Identify target industries (e.g., financial services, government contractors) or countries of interest.
    2. Filter by Advanced DNS Records: Use WebTrackly's advanced filters to search for domains with has_caa_record: true, has_dane_record: true, or has_svcb_https_record: true. You can further filter by specific certificate authorities (e.g., "Let's Encrypt" via CAA records) or certificate properties.
    3. Combine with Technology & Geolocation: Enrich this data by adding filters for specific web server technologies (e.g., Nginx, Apache, IIS) or cloud providers (e.g., AWS, Azure) and geographical location.
    4. Analyze Trends: Export the dataset and use data science tools (Python, R) to analyze adoption rates, common misconfigurations, or regional differences in the implementation of these security standards.
    5. Identify Vulnerabilities (Ethical Hacking): For domains with CAA records, check if unauthorized CAs are attempting to issue certificates. For DANE, verify if the published certificate hash matches the live certificate.
  • Expected Results:
    • Discovery of specific security trends: For example, identifying that 15% of financial institutions in Germany are actively deploying DANE, indicating a mature security stance.
    • Identification of potential weak points: Spotting industries or regions where advanced DNS security adoption is lagging, highlighting areas for targeted security product development or awareness campaigns.
    • Creation of robust threat intelligence feeds: Continuously monitor changes in these records for target organizations, providing early warnings for certificate mis-issuance or security policy changes.

4. For Data Scientists & Engineers: Building Robust Datasets for Web Infrastructure Trend Analysis

  • Target Audience: Data scientists, data engineers, and researchers building large-scale web datasets for academic studies, market analysis, or internal product development.
  • Problem: Acquiring clean, structured, and comprehensive data on web infrastructure, including DNS records and HTTPS status, for millions of domains. Traditional web scraping is resource-intensive, legally complex, and often yields inconsistent data.
  • Solution with WebTrackly:
    1. Define Data Requirements: Specify the exact fields needed: domain, IP address, A/AAAA records, CNAME, MX, NS, TXT, CAA, TLSA, SVCB/HTTPS records, HTTPS status, certificate issuer, hosting provider, CMS, country, etc.
    2. Leverage WebTrackly API: Use the WebTrackly API to programmatically query and download large datasets based on desired filters (e.g., all domains in the US with HTTPS, or all domains globally with CAA records).
    3. Batch Processing: Utilize WebTrackly's bulk download capabilities for initial large dataset acquisition, then use the API for incremental updates.
    4. Integrate into Data Pipelines: Automatically feed the extracted data into a data warehouse (e.g., Snowflake, BigQuery) or a data lake for further processing, normalization, and integration with other datasets.
    5. Analyze & Model: Apply machine learning models to identify correlations between DNS configurations, HTTPS adoption, technology stacks, and business success metrics.
  • Expected Results:
    • Reduction in data acquisition time by 90%: Eliminating the need for custom scrapers and infrastructure.
    • Access to a consistent, high-quality dataset of 200M+ domains, updated regularly, enabling more reliable trend analysis.
    • Discovery of novel insights: For example, correlating the adoption of SVCB/HTTPS records with faster website load times and higher conversion rates across specific industries. This allows for predictive modeling of technology trends.

5. For Enterprise Sales: Uncovering High-Value Prospects Based on Certificate Authority and Hosting Provider

  • Target Audience: Enterprise sales teams selling specialized cloud services, advanced security solutions, or managed hosting.
  • Problem: Identifying large organizations that are likely to have complex IT environments and a budget for premium services. Simply knowing "they use HTTPS" isn't enough; the type of certificate authority and the hosting provider can signal enterprise-level operations.
  • Solution with WebTrackly:
    1. Filter by HTTPS Status & Certificate Authority: Start by filtering for has_https: true. Then, crucially, filter by specific Certificate Authorities (CAs) that typically serve enterprise clients (e.g., DigiCert, Sectigo, GlobalSign, Thawte) rather than free CAs like Let's Encrypt. This immediately narrows the focus to organizations investing in premium security.
    2. Combine with Hosting Provider: Further refine by filtering for specific enterprise cloud providers (e.g., AWS, Azure, Google Cloud, Oracle Cloud Infrastructure) or large managed hosting providers.
    3. Identify Key Technologies: Layer on filters for specific enterprise-grade technologies (e.g., SAP, Oracle, Adobe Experience Manager, specific CRMs or ERPs).
    4. Geographic & Industry Segmentation: Apply country and industry filters to pinpoint target markets.
    5. Extract Verified Contacts: Obtain direct contact information for IT Directors, CIOs, or Procurement Managers.
  • Expected Results:
    • Creation of highly qualified enterprise lead lists: Reducing the noise of small businesses and hobby sites.
    • Increased average deal size: Targeting companies already demonstrating investment in their infrastructure and security.
    • Improved sales team efficiency: By focusing efforts on prospects with a higher propensity to buy premium services, based on their observable technology and security choices. For instance, identifying 5,000 domains in North America using DigiCert on AWS is a goldmine for an enterprise cloud security vendor.

Demystifying the Data: WebTrackly Output Examples

To truly understand the power of WebTrackly, it's essential to see the kind of data it delivers. The following tables illustrate sample outputs and a comparison with alternatives, highlighting the depth and breadth of insights available.

Table 1: Sample Domain Intelligence Data with HTTPS & DNS Insights

This table shows a snapshot of enriched domain data, focusing on how dns record https insights are integrated with other crucial intelligence points.

Domain CMS/Technology Country Server Emails Found Hosting Provider HTTPS Status Cert Issuer CAA Record DANE (TLSA) SVCB/HTTPS
examplecorp.com WordPress, WooCommerce US Nginx 2 AWS True Let's Encrypt True False False
securepayments.net Custom, Node.js UK Cloudflare 3 Google Cloud True DigiCert True True True
globaltrends.de HubSpot CMS DE Apache 1 Hetzner True Sectigo True False False
innovatex.ca Shopify CA Shopify 0 Shopify True Cloudflare False False True
datahub.io Custom, Python/Django IE Nginx 4 DigitalOcean True GlobalSign True True False
oldschoolbiz.com Joomla US Apache 1 GoDaddy False N/A False False False
fintechsolutions.jp Custom, Java Spring JP Tomcat 2 Azure True Entrust True False True
localbakery.fr SquareSpace FR Squarespace 0 Squarespace True Let's Encrypt False False False
govportal.gov Drupal AU IIS 5 GovCloud True Thawte True True False
healthtech.ch Webflow CH Netlify 1 Netlify True Google Trust Services False False False

Interpretation: Notice how securepayments.net and datahub.io stand out with both CAA and DANE (TLSA) records, indicating a strong commitment to security beyond basic HTTPS. innovatex.ca and fintechsolutions.jp are leveraging the newer SVCB/HTTPS records, signaling modern infrastructure. oldschoolbiz.com immediately flags as a potential risk or outdated business due to lack of HTTPS. This granular data allows for highly specific segmentation.

Table 2: WebTrackly vs. Competitor Comparison for Domain Intelligence

This table highlights WebTrackly's competitive advantages in the domain intelligence space, particularly concerning the depth of DNS and HTTPS data.

Feature / Platform WebTrackly.com BuiltWith.com Wappalyzer.com SimilarTech.com
Domain Coverage 200M+ Domains ~670M Domains (Focus on top sites) ~100M Domains ~100M Domains
Data Freshness Daily/Weekly for active sites, monthly full scans Weekly/Monthly Weekly/Monthly Monthly
HTTPS Status Detection Live scan + Certificate details Yes, basic status Yes, basic status Yes, basic status
DNS Record Depth A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, DANE (TLSA), SVCB/HTTPS A, CNAME, MX, NS, TXT (Limited advanced records) Basic A, CNAME Basic A, CNAME
Certificate Authority Detection Yes, detailed issuer & expiration Limited No No
Hosting Provider Detection Highly accurate, granular (cloud, shared, dedicated) Good Basic Good
Technology Detection 1500+ technologies 60,000+ technologies (incl. obscure) 2000+ technologies 1000+ technologies
Contact Extraction Verified B2B emails & phone numbers Limited, often generic No No
Filtering Capabilities Extensive (tech, country, hosting, DNS, HTTPS, contacts, etc.) Extensive (tech, country, spend) Basic (tech, country) Basic (tech, country, traffic)
API Access Comprehensive, high-volume Comprehensive Limited Comprehensive
Pricing Model Flexible, usage-based, bulk datasets Tiered subscriptions, higher entry cost Tiered subscriptions, per-lookup Enterprise focus, custom quotes
Target Audience Focus B2B Sales, Marketing, SEO, Data Science, Cybersecurity Sales, Marketing, Investors Developers, Marketers Sales, Marketing, Investors

Conclusion: WebTrackly stands out with its unparalleled depth in DNS record analysis, including advanced security-focused records like CAA, DANE (TLSA), and SVCB/HTTPS. This, combined with verified contact extraction and massive domain coverage, positions it as the superior choice for professionals demanding granular, actionable web intelligence.

Step-by-Step Tutorial: Extracting Secure Domain Data with WebTrackly

Leveraging WebTrackly to find domains based on their DNS records and HTTPS status is straightforward, whether you prefer a graphical interface or programmatic API access. Here's how to accomplish the main task of identifying secure, high-value leads.

1. Using the WebTrackly Domain Search Interface

The WebTrackly web interface provides a powerful, intuitive way to filter and explore our dataset of 200M+ domains.

Goal: Find all e-commerce domains in the US that use HTTPS and have a CAA record, indicating active certificate management, and then extract their business contacts.

  1. Navigate to Domain Search: Go to WebTrackly's Domain Search.
  2. Apply Technology Filter: In the "Technologies" filter section, search for and select relevant e-commerce platforms. For example, type "Shopify" and select it. You can add more, like "WooCommerce" or "Magento."
  3. Apply Country Filter: In the "Country" filter, type "United States" and select it.
  4. Enable HTTPS Filter: Look for the "HTTPS Status" filter (often under "Security" or "General"). Select "Yes" or ensure has_https is checked.
  5. Add DNS Record Filter (CAA): Under "DNS Records" or "Advanced Filters," locate the option for "CAA Record Present" or has_caa_record. Select "Yes" or check the box.
  6. Refine with Contact Filters (Optional but Recommended): To ensure actionable leads, you might also want to filter for domains that has_email: true or has_phone: true.
  7. Review Results: The platform will instantly display the number of matching domains. Browse the results to get a feel for the data.
  8. Export Your Data: Click the "Export" button. You'll typically have options to export all fields or select specific ones. Choose CSV for easy integration into spreadsheets or CRMs. For very large datasets, the system might prepare the export in the background and notify you when it's ready for download.

This process allows you to quickly generate a highly targeted list of secure e-commerce businesses actively managing their certificate issuance, providing a strong signal of their operational maturity.

2. Leveraging the WebTrackly API for Programmatic Access

For data scientists, engineers, or those needing to integrate WebTrackly data into automated workflows, the API offers unparalleled flexibility and scale.

Goal: Programmatically retrieve all domains in Germany using WordPress, with HTTPS, and specifically having DANE (TLSA) records, then get their contact emails.

Prerequisites:
* A WebTrackly API key (obtainable from your account dashboard).
* A tool like curl (for command-line examples) or a programming language (Python, Node.js) with an HTTP client library.

API Endpoint Structure (Simplified Example):
The WebTrackly API typically uses endpoints like /api/v1/domains/search/ for filtering and retrieval.

Example API Call (using curl):

# First, let's look for domains in Germany using WordPress and HTTPS.
# Then, we'll refine by DANE (TLSA) records and request contact emails.

curl -X GET \
  -H "Authorization: Bearer YOUR_API_KEY" \
  "https://api.webtrackly.com/v1/domains/search/? \
  country=DE& \
  technology=wordpress& \
  has_https=true& \
  has_dane_record=true& \
  fields=domain,country,has_https,certificate_issuer,has_dane_record,emails& \
  limit=100& \
  offset=0"

Explanation of Parameters:

  • -X GET: Specifies an HTTP GET request.
  • -H "Authorization: Bearer YOUR_API_KEY": Replaces YOUR_API_KEY with your actual WebTrackly API key for authentication.
  • country=DE: Filters for domains located in Germany.
  • technology=wordpress: Filters for domains detected as using WordPress.
  • has_https=true: Filters for domains that actively use HTTPS.
  • has_dane_record=true: Crucially, filters for domains that have a DANE (TLSA) DNS record. This is a strong indicator of advanced security.
  • fields=domain,country,has_https,certificate_issuer,has_dane_record,emails: Specifies the exact fields you want in the response, optimizing bandwidth and data processing.
  • limit=100: Retrieves up to 100 results per request. You'll use offset for pagination to get more.
  • offset=0: Starts from the first result.

Example API Call (Python):

import requests
import json

api_key = "YOUR_API_KEY"
base_url = "https://api.webtrackly.com/v1/domains/search/"

params = {
    "country": "DE",
    "technology": "wordpress",
    "has_https": True,
    "has_dane_record": True,
    "fields": "domain,country,has_https,certificate_issuer,has_dane_record,emails",
    "limit": 100,
    "offset": 0
}

headers = {
    "Authorization": f"Bearer {api_key}"
}

all_results = []
while True:
    response = requests.get(base_url, headers=headers, params=params)
    response.raise_for_status() # Raise an exception for HTTP errors
    data = response.json()

    if not data['results']:
        break

    all_results.extend(data['results'])

    # Check for next page URL or if we've reached the end
    if 'next' in data and data['next']:
        params['offset'] += params['limit']
    else:
        break

# Process your results
for domain_data in all_results:
    print(f"Domain: {domain_data.get('domain')}")
    print(f"  Country: {domain_data.get('country')}")
    print(f"  HTTPS: {domain_data.get('has_https')}")
    print(f"  Cert Issuer: {domain_data.get('certificate_issuer')}")
    print(f"  Has DANE Record: {domain_data.get('has_dane_record')}")
    print(f"  Emails: {', '.join(domain_data.get('emails', [])) if domain_data.get('emails') else 'N/A'}\n")

print(f"Total domains found: {len(all_results)}")

This Python script demonstrates how to paginate through results, ensuring you can retrieve large datasets efficiently and integrate them into your data processing workflows. The ability to filter by has_dane_record (or has_caa_record, has_svcb_https_record) directly in the API call unlocks a new level of granular targeting based on advanced dns record https intelligence.

Common Mistakes in Leveraging DNS & HTTPS Data and How to Avoid Them

Even with powerful tools like WebTrackly, practitioners can make mistakes that diminish the value of their domain intelligence efforts. Understanding these pitfalls and implementing corrective strategies is crucial for maximizing your ROI.

Mistake 1: Confusing DNS Records with Active HTTPS Status

  • What goes wrong: Assuming that the presence of certain DNS records (like A records pointing to an IP) automatically means a website uses HTTPS, or conversely, that the absence of advanced DNS security records means no HTTPS.
  • Why it goes wrong: DNS records primarily direct traffic. The actual HTTPS connection and certificate validation happen at the server level (on port 443). A domain can have perfect DNS records but still serve content over plain HTTP if the server isn't configured correctly or lacks an SSL certificate.
  • The fix: Always combine DNS record analysis with a live check for HTTPS status. WebTrackly does this automatically by performing real-time scans to confirm HTTPS presence and extract certificate details, then cross-referencing with DNS records for a complete picture. Filter explicitly for has_https: true alongside any DNS record filters.

Mistake 2: Ignoring Advanced Security-Related DNS Records (CAA, DANE, SVCB/HTTPS)

  • What goes wrong: Focusing only on basic DNS records (A, MX) and a simple HTTPS true/false status, thereby missing critical signals about a domain's security posture and maturity.
  • Why it goes wrong: CAA records tell you about certificate issuance policies. DANE (TLSA) records offer robust certificate pinning. SVCB/HTTPS records indicate modern, optimized secure connections. Ignoring these means you're missing powerful segmentation criteria for cybersecurity research, enterprise sales, or identifying early adopters.
  • The fix: Actively incorporate filters for has_caa_record, has_dane_record, and has_svcb_https_record in your WebTrackly searches. Use these as high-value indicators for specific use cases, such as targeting security-conscious organizations or those with cutting-edge web infrastructure.

Mistake 3: Relying on Stale or Incomplete Data Sources

  • What goes wrong: Using outdated domain intelligence platforms or performing infrequent manual lookups, leading to inaccurate lead lists, flawed market analysis, and missed opportunities. DNS records and HTTPS configurations can change frequently.
  • Why it goes wrong: The web is dynamic. Domains change hosting, update their certificates, implement new security policies, or even go offline. Data that's weeks or months old can be significantly misleading.
  • The fix: Prioritize platforms with high data freshness. WebTrackly's entire infrastructure is built for continuous scanning and updates, ensuring our 200M+ domain database reflects the most current DNS records and HTTPS statuses. For critical targets, use our API to query for the latest information on demand.

Mistake 4: Failing to Combine DNS Data with Other Technology Detections

  • What goes wrong: Analyzing DNS and HTTPS data in isolation, without cross-referencing it with other technology detections (CMS, analytics, CRM). This leads to a narrow view and limits the actionable insights.
  • Why it goes wrong: A domain's security posture (from DNS/HTTPS) gains much more context when combined with its core technologies. For example, a Shopify store with DANE records is a different lead than a custom-built site with the same security.
  • The fix: Always use WebTrackly's multi-faceted filtering. Combine has_https, has_caa_record, and certificate_issuer with technology (e.g., "Shopify"), hosting_provider (e.g., "AWS"), and country. This creates a holistic profile for each domain, enabling hyper-targeted campaigns.

Mistake 5: Overlooking Subdomains and Their Unique Security Postures

  • What goes wrong: Only analyzing root domains, neglecting the fact that subdomains (e.g., blog.example.com, shop.example.com) often have entirely different hosting, technologies, and security configurations.
  • Why it goes wrong: Subdomains can be hosted on different servers, use different CMSs, and sometimes even have different certificate authorities or security policies. Missing these means missing potential leads or security vulnerabilities.
  • The fix: WebTrackly indexes both root domains and significant subdomains. When performing research, consider broadening your scope to include subdomains where relevant. For lead generation, analyze subdomains as potential independent business units or departments with distinct needs.

Mistake 6: Misinterpreting Certificate Information Without Context

  • What goes wrong: Drawing conclusions about a domain's trustworthiness or size solely based on the certificate issuer (e.g., assuming a site using Let's Encrypt is less credible than one using DigiCert).
  • Why it goes wrong: While free certificates like Let's Encrypt have democratized HTTPS, many large, highly credible organizations (e.g., GitHub, Cloudflare, major SaaS providers) use them for parts of their infrastructure. The key is context. A small blog using a premium EV certificate might be overkill, while a large enterprise using Let's Encrypt but with DANE records indicates sophisticated management.
  • The fix: Use certificate issuer as one data point among many. Combine it with hosting provider, detected technologies, and especially advanced dns record https (CAA, DANE) to build a more accurate picture of a domain's overall security and operational maturity.

Mistake 7: Neglecting Scalability in Data Collection and Analysis

  • What goes wrong: Designing workflows that work for a few hundred domains but break down when faced with tens of thousands or millions, leading to bottlenecks and lost opportunities.
  • Why it goes wrong: Manual processes, custom-built scrapers that require constant maintenance, or tools with limited API quotas are not designed for the scale of the modern web.
  • The fix: Architect your data strategy around a scalable platform like WebTrackly. Utilize its powerful filtering interface for quick exploration and its robust API for bulk data extraction and integration into your existing data pipelines. This ensures you can grow your intelligence efforts without hitting technical ceilings.

Tools & Integrations: Powering Your Workflow with WebTrackly Data

The real power of WebTrackly's DNS and HTTPS data comes from its ability to integrate seamlessly into your existing sales, marketing, and data science workflows. Stop juggling spreadsheets and manual lookups; automate the flow of intelligence directly into the tools you use every day.

CRM Integration (HubSpot, Salesforce)

Your CRM is the central hub for customer interactions. Enriching it with WebTrackly's detailed domain intelligence, including HTTPS status, certificate details, and advanced DNS records, supercharges your sales and account management efforts.

  • CSV Import: The simplest method. Export your filtered lead lists from WebTrackly as a CSV. Most CRMs (HubSpot, Salesforce, Zoho CRM, Pipedrive) have robust CSV import features that allow you to map WebTrackly's fields (e.g., domain, has_https, certificate_issuer, emails, hosting_provider, has_caa_record) directly to custom fields in your CRM. This enriches existing accounts or creates new, highly detailed lead records.
  • API Integration: For automated, real-time enrichment, use WebTrackly's API to push data directly into your CRM.
    • Scenario: When a new lead enters your CRM, a webhook or scheduled script can trigger an API call to WebTrackly using the lead's domain. WebTrackly returns the full domain profile, which is then updated in the CRM.
    • Custom Development: This typically requires a developer to write scripts (e.g., in Python or Node.js) that interact with both WebTrackly's and your CRM's APIs. For Salesforce, you might use Apex or external integration platforms. For HubSpot, their API is developer-friendly.
  • Benefits:
    • Enhanced Lead Scoring: Automatically score leads higher if they meet specific criteria (e.g., has_https: true, enterprise CA, DANE records).
    • Personalized Outreach: Sales reps have immediate access to a prospect's tech stack and security posture, allowing for hyper-personalized messaging that resonates.
    • Account Prioritization: Identify high-value accounts based on their advanced infrastructure, enabling reps to focus on the most promising opportunities.

Email Outreach Platforms (Lemlist, Instantly)

Once you've identified your target domains and extracted contacts, the next step is effective outreach. WebTrackly data makes your email campaigns significantly more potent.

  • CSV Import: Export your WebTrackly list, including domain, emails, first_name, last_name, and relevant tech/security fields. Import this CSV into email outreach tools like Lemlist, Instantly, Salesloft, or Outreach.
  • Dynamic Customization: Use WebTrackly's data fields to populate custom variables in your email templates.
    • Example: "Hi {{first_name}}, I noticed your company, {{company_name}}, is using {{technology}} and has implemented advanced certificate management with a {{certificate_issuer}} certificate. Our solution helps {{technology}} users like you further enhance their security..."
  • Benefits:
    • Higher Open Rates: Personalized subject lines leveraging specific tech/security details stand out.
    • Increased Reply Rates: Relevant, data-driven messages demonstrate that you've done your homework and understand their specific context.
    • Reduced Spam Flags: Targeting highly qualified leads with relevant messages improves engagement and sender reputation.

Data Warehouses & Business Intelligence Tools

For data scientists, analysts, and large enterprises, integrating WebTrackly data into your central data warehouse (e.g., Snowflake, Google BigQuery, Amazon Redshift) or BI tools (e.g., Tableau, Power BI) unlocks advanced analytics and reporting.

  • Bulk Download / API Integration: Use WebTrackly's bulk dataset downloads or its API to feed massive amounts of domain intelligence directly into your data lake or warehouse. Schedule daily or weekly API calls to keep your internal datasets fresh.
  • ETL Pipelines: Build Extract, Transform, Load (ETL) pipelines to ingest, clean, and enrich WebTrackly data. Combine it with your internal sales data, customer success metrics, and marketing campaign performance for a unified view.
  • Analytics & Reporting:
    • Market Share Analysis: Track the adoption of specific technologies, hosting providers, or advanced dns record https (like DANE) across industries and geographies.
    • Trend Identification: Predict future technology shifts by monitoring early adopters of new security standards.
    • Competitive Benchmarking: Compare your company's market share or security posture against competitors based on objective web data.
  • Benefits:
    • Single Source of Truth: Centralize all domain intelligence for consistent reporting and analysis.
    • Strategic Insights: Drive high-level business decisions with data-backed insights into market trends and competitive landscapes.
    • Predictive Modeling: Develop models to forecast technology adoption, identify churn risks, or predict sales opportunities.

WebTrackly vs. The Competition: A Clear Advantage

While tools like BuiltWith, Wappalyzer, and SimilarTech offer technology detection, WebTrackly provides several critical advantages, especially concerning dns record https intelligence:

  • Granular DNS Data: WebTrackly doesn't just provide basic A records. We go deep, capturing CAA, DANE (TLSA), and SVCB/HTTPS records, which are often overlooked by competitors but are critical for advanced security and infrastructure analysis.
  • Comprehensive HTTPS & Certificate Details: Beyond a simple "HTTPS: Yes," WebTrackly extracts certificate issuer, expiration, and other details, allowing for more nuanced filtering (e.g., "domains using DigiCert").
  • Verified Contact Extraction: Most competitors focus solely on technology. WebTrackly integrates verified B2B contact extraction directly into the platform, turning intelligence into actionable leads.
  • Scale and Freshness: With 200M+ domains scanned and updated frequently, WebTrackly offers a broader and fresher dataset than many competitors, especially for the long tail of the web.
  • Targeted for B2B: Our platform is specifically designed for the needs of B2B sales, marketing, and data science teams, providing the filters and data points that directly translate into business value.

By integrating WebTrackly, you're not just getting data; you're getting a strategic advantage that translates into more efficient operations and higher revenue.

Quantifying the Gain: ROI Calculation with WebTrackly's Secure Domain Data

Let's break down the tangible return on investment (ROI) you can expect by leveraging WebTrackly's advanced DNS and HTTPS data for lead generation. We'll compare a hypothetical scenario before and after adopting WebTrackly.

Scenario: A B2B SaaS company selling a website security product (e.g., WAF, CDN with advanced security features) targets mid-market businesses. They aim to find companies that are security-conscious but might not yet have their specific solution.

Before WebTrackly:

  • Lead Source: Generic lists from industry directories, manual website browsing, basic LinkedIn searches.
  • Qualification Process:
    • Manually check if a website uses HTTPS (basic check).
    • Manually visit websites to infer technology or hosting.
    • Manually search for contact information (often generic info@ emails).
    • Estimate: 10 minutes per lead for qualification and contact finding.
  • SDR Productivity: An SDR can qualify approximately 40 leads per day (8 hours * 60 minutes / 10 minutes per lead).
  • Lead Quality: Low. Many leads don't have the right tech stack, are too small, or don't demonstrate a high enough security commitment. Let's say 10% are truly qualified.
  • Cost per Qualified Lead (CPL):
    • SDR Fully Loaded Cost: $5,000/month.
    • Leads per month: 40 leads/day * 20 days = 800 leads.
    • Qualified Leads per month: 800 * 10% = 80 qualified leads.
    • CPL: $5,000 / 80 = $62.50 per qualified lead.
  • Conversion Rate: Due to low lead quality, let's assume a 1% conversion rate from qualified lead to closed-won deal.
  • Average Deal Value (ADV): $15,000 (Annual Contract Value).
  • Revenue from 80 qualified leads: 80 * 1% * $15,000 = $12,000 per month.

After WebTrackly (using DNS and HTTPS filters):

  • Lead Source: WebTrackly's 200M+ domain database, filtered by:
    • has_https: true
    • has_caa_record: true (indicates active certificate management)
    • hosting_provider (e.g., AWS, Azure, Google Cloud – signals enterprise infrastructure)
    • has_email: true and has_phone: true (verified contacts)
    • Target country and relevant technologies.
  • Qualification Process:
    • WebTrackly pre-qualifies leads based on all specified criteria.
    • SDRs receive a ready-to-use list with full tech profiles and contacts.
    • Estimate: 1 minute per lead for review and minor enrichment (e.g., adding a personal note).
  • SDR Productivity: An SDR can review approximately 480 leads per day (8 hours * 60 minutes / 1 minute per lead).
  • Lead Quality: High. Leads are pre-qualified based on robust technical and security indicators. Let's say 50% are truly qualified for outreach.
  • Cost per Qualified Lead (CPL):
    • SDR Fully Loaded Cost: $5,000/month.
    • WebTrackly Monthly Cost: ~$500 (example for a mid-tier plan with extensive data and contacts).
    • Total Cost: $5,500/month.
    • Leads per month from WebTrackly: Easily generate 10,000+ leads, but let's focus on what an SDR can process.
    • Qualified Leads per month (SDR capacity): 480 leads/day * 20 days = 9,600 leads generated by WebTrackly, 50% qualified = 4,800 leads. However, an SDR can only process ~480 leads/day. So let's cap at the SDR's daily processing capacity for qualified leads from the generated list, meaning they can outreach to 9,600 leads if they are 100% qualified, but let's say they still process 800 qualified leads a month for comparison purposes (meaning they are selecting the best 800 from WebTrackly's vast, highly qualified pool).
    • Correction for comparison: The SDR's capacity is still 800 leads processed for outreach, but now those 800 are highly qualified.
    • CPL: $5,500 / 800 = $6.88 per highly qualified lead. (A dramatic drop from $62.50)
  • Conversion Rate: Due to significantly higher lead quality and personalization, let's assume a 3% conversion rate from qualified lead to closed-won deal.
  • Average Deal Value (ADV): Still $15,000.
  • Revenue from 800 highly qualified leads: 800 * 3% * $15,000 = $36,000 per month.

ROI Calculation:

  • Increased Revenue: $36,000 (After) - $12,000 (Before) = $24,000 increase per month.
  • Net Profit Increase (considering WebTrackly cost): $24,000 - $500 = $23,500 per month.
  • ROI (Monthly): ($23,500 / $500) * 100% = 4700% ROI.

This conservative calculation demonstrates that for a typical B2B SaaS company, WebTrackly pays for itself many times over within the first month. The time saved, the drastic improvement in lead quality, and the subsequent boost in conversion rates make it an indispensable tool for revenue growth.

Frequently Asked Questions (FAQ)

Q: How fresh is WebTrackly's DNS and HTTPS data?

A: WebTrackly maintains one of the freshest domain intelligence databases in the industry. Our automated crawlers continuously scan and re-index over 200 million domains. For active websites, data (including DNS records and HTTPS status) is typically updated daily or weekly. Our entire dataset undergoes a full refresh monthly to capture changes across the entire web. This ensures you're always working with the most current information available.

Q: What data formats are available for export and API access?

A: WebTrackly offers flexible data export options. Through our web interface, you can export filtered lists as standard CSV (Comma Separated Values) files, which are easily imported into spreadsheets, CRMs, or other business tools. For programmatic access, our comprehensive API provides data in JSON (JavaScript Object Notation) format, ideal for integration into custom applications, data pipelines, and analytical platforms.

Q: What specific filtering capabilities does WebTrackly offer for DNS and HTTPS?

A: Our filtering capabilities are incredibly granular:
* HTTPS Status: Filter by has_https: true or false.
* Certificate Issuer: Filter by specific Certificate Authorities (e.g., "Let's Encrypt", "DigiCert", "Sectigo", "Cloudflare").
* DNS Records: Filter by the presence or absence of key records, including has_caa_record, has_dane_record (TLSA), has_svcb_https_record, has_mx_record, has_txt_record, etc.
* Other: Combine these with filters for CMS, country, hosting provider, IP address, technology stack, detected business emails, phone numbers, and more, enabling highly specific segmentation.

Q: How does WebTrackly's pricing work, and what are the differences between plans?

A: WebTrackly offers flexible, usage-based pricing designed to scale with your needs. Our plans typically differentiate based on the volume of data lookups/exports, the number of contacts extracted, and access to advanced features like API rate limits, bulk dataset downloads, and premium support. We have starter plans for individual users and growing businesses, all the way up to enterprise solutions with custom agreements for massive data requirements. Details are available on our Pricing Plans page.

Q: How accurate is WebTrackly's data, and what methodology is used for HTTPS detection?

A: WebTrackly prides itself on high data accuracy. Our methodology for HTTPS detection involves:
1. DNS Resolution: We first resolve the domain's A/AAAA records to get its IP address.
2. Live Connection Attempt: We then attempt a connection to the resolved IP address on port 443 (the standard for HTTPS).
3. TLS Handshake & Certificate Analysis: If a connection is established, we perform a TLS handshake to verify the SSL/TLS certificate. We extract details such as the certificate issuer, validity period, and common name.
4. Redirection Handling: We follow HTTP to HTTPS redirects to accurately determine the final secure status.
This active, real-time scanning, combined with our comprehensive DNS record parsing, ensures highly accurate and up-to-date HTTPS and security-related data.

Q: Is WebTrackly's data collection and usage GDPR compliant?

A: Yes, WebTrackly is committed to GDPR and other relevant data privacy regulations. Our data collection focuses on publicly available information (like DNS records, website technologies, and publicly listed business contact information). We do not collect personal data from website visitors. All business contact information is obtained from public sources and is validated for business use. We adhere to strict data handling and privacy policies to ensure compliance.

Q: Can I integrate WebTrackly data directly into my existing CRM or sales tools?

A: Absolutely. WebTrackly is built for seamless integration. You can export filtered data as CSV files for easy import into popular CRMs like HubSpot, Salesforce, Zoho CRM, Pipedrive, and more. For more advanced, automated workflows, our robust API allows for direct integration into your CRM, sales engagement platforms (e.g., Lemlist, Instantly), data warehouses, or custom-built applications. We provide comprehensive API documentation to guide your development efforts.

Q: How does WebTrackly compare to competitors like BuiltWith or Wappalyzer for DNS and HTTPS intelligence?

A: WebTrackly offers distinct advantages:
* Deeper DNS Insights: We capture a broader range of advanced DNS records (CAA, DANE/TLSA, SVCB/HTTPS) that many competitors overlook, providing more granular security intelligence.
* Comprehensive Certificate Details: Beyond basic HTTPS status, we provide certificate issuer and other details, enabling more refined filtering.
* Integrated Contact Data: Unlike many tech profilers, WebTrackly includes verified B2B contact extraction, turning insights directly into actionable leads.
* Scale and Freshness: With 200M+ domains and frequent updates, WebTrackly provides a more extensive and current view of the web.
Our focus is on providing actionable, B2B-specific intelligence, making WebTrackly a more powerful tool for lead generation, competitive analysis, and market research.

Q: Does WebTrackly provide historical DNS and HTTPS data?

A: While WebTrackly's primary focus is on providing the freshest, most up-to-date data, we do retain snapshots of historical data for key attributes, including DNS records and HTTPS status, for a certain period. This allows for basic trend analysis and tracking changes over time for specific domains. For detailed historical datasets or long-term trend analysis, please contact our sales team to discuss enterprise data solutions.

Q: Can WebTrackly identify domains with specific certificate authorities (CAs)?

A: Yes, absolutely. WebTrackly's HTTPS detection process includes identifying the Certificate Authority (CA) that issued the SSL/TLS certificate for each domain. You can easily filter our 200M+ domain database to find domains that use specific CAs, such as "Let's Encrypt," "DigiCert," "Sectigo," "Cloudflare," "GlobalSign," or any other recognized CA. This capability is invaluable for segmenting prospects by their security investment level or for competitive analysis of CA market share.

Conclusion: Secure Your Strategy, Secure Your Growth

In the relentless pursuit of market advantage, the ability to dissect and understand web infrastructure at scale is no longer a luxury – it's a necessity. The intricate relationship between dns record https provides a goldmine of actionable intelligence, allowing you to move beyond surface-level analysis and tap into the core operational DNA of millions of businesses.

By leveraging WebTrackly, you gain:

  • Unprecedented Lead Quality: Filter 200M+ domains by specific DNS records, HTTPS status, certificate issuers, and other technologies to pinpoint your ideal customer profile with surgical precision.
  • Superior Competitive Intelligence: Monitor competitor technology stacks, security postures, and hosting choices, identifying strategic opportunities and potential vulnerabilities.
  • Accelerated Data-Driven Decisions: Access fresh, comprehensive data via a user-friendly interface or robust API, powering your sales, marketing, and data science initiatives with unparalleled efficiency.
  • Significant ROI: Transform manual, time-consuming research into an automated, high-impact revenue engine, dramatically reducing your cost per qualified lead and boosting conversion rates.

Stop guessing. Start knowing. WebTrackly empowers you to uncover the hidden signals in the web's infrastructure, turning complex technical data into clear, actionable business opportunities.

Ready to find your next 10,000 leads?
WebTrackly's domain intelligence platform lets you search 200M+ domains by technology, hosting, country, and contacts.
Start Free → | View Pricing →

Related Resources

Share this post

Related Posts

Comments (0)

Leave a Comment

No comments yet. Be the first to comment!

support_agent
WebTrackly Support
Usually replies within minutes
Hi there!
Send us a message and we'll reply ASAP.