Product News

Introducing the Markmonitor Integration for CloudQuery

•

5 min read

CloudQuery now syncs domain data from Markmonitor into your data warehouse. Track domain expirations, audit DNSSEC coverage, and cross-reference nameserver assignments against your DNS infrastructure - all with SQL alongside your other cloud resources.

We've added a new source integration: Markmonitor. If your organization manages a domain portfolio through Markmonitor, this puts that data into your data warehouse alongside the rest of your cloud asset inventory.

What Is Markmonitor? #

Markmonitor is an enterprise domain management platform used by large organizations to register and protect their domain names - especially high-value corporate domains that need protection against expiration lapses, unauthorized transfers, and hijacking. Many organizations with significant brand presence manage dozens to hundreds of domains through Markmonitor across different TLDs and business units.

The data problem is straightforward: until now, your domain registrar data lived in a separate silo from your cloud infrastructure. You'd need to log into a separate dashboard to check expiration dates or audit DNS security configuration. This integration changes that.

What Tables Does the Markmonitor Integration Sync? #

Three tables come with the integration.

markmonitor_domain_details is the primary table. It stores domain names, expiration dates, domain IDs, and registration status. This is your domain inventory - the starting point for most queries.

markmonitor_domain_dnssec captures DNSSEC (DNS Security Extensions) configuration per domain, including DNSSEC type and the signing algorithm in use. If you're auditing DNS security posture across your portfolio, this is the table you want.

markmonitor_domain_nameservers stores nameserver assignments for each domain. Cross-referencing this against your actual DNS provider records is a quick way to catch drift - cases where what Markmonitor shows doesn't match what's actually serving DNS.

What Can You Query? #

How Do I Track Domain Expirations Before They Lapse? #

Domain expiration is the kind of thing that only becomes visible when it's already a problem. A lapsed domain is at best an embarrassing outage; at worst, it's a security incident where someone else picks up the registration.

This query pulls domains expiring in the next 90 days:

SELECT domain_name,
       date_expires,
       (date_expires::date - CURRENT_DATE) AS days_until_expiration
FROM markmonitor_domain_details
WHERE date_expires::date < CURRENT_DATE + INTERVAL '90 days'
ORDER BY days_until_expiration;

Set this up as a CloudQuery Policy and you've got a continuous check that runs on every sync. If you're also tracking SSL certificate expiration in AWS, domain expiration monitoring pairs well with it - covering both the certificate and the registration layer.

How Do I Audit DNSSEC Coverage Across My Domain Portfolio? #

DNSSEC isn't universally required, but for organizations in regulated industries or with high-value brand domains, having it configured correctly matters. This query shows which domains have DNSSEC enabled and what signing algorithms they're using:

SELECT d.domain_name,
       s.type,
       s.algorithm
FROM markmonitor_domain_details d
JOIN markmonitor_domain_dnssec s ON d.domain_id = s.domain_id
ORDER BY d.domain_name;

Run the inverse - domains in markmonitor_domain_details with no matching row in markmonitor_domain_dnssec - to find domains where DNSSEC isn't configured at all. If you're thinking about domain security as part of a broader attack surface management strategy, this kind of gap analysis is a good starting point.

How Can I Cross-Reference Markmonitor With My DNS Provider? #

This is where the integration starts to get interesting. If you're already syncing AWS data with the AWS integration, you can join Markmonitor domain records against Route 53 hosted zones to find:

Domains registered in Markmonitor with no corresponding hosted zone in Route 53 (orphaned registrations that may have been forgotten)
Hosted zones in Route 53 that don't appear in your Markmonitor inventory (domains registered through other registrars that might need centralized management)

Same approach applies if you're syncing Cloudflare - join markmonitor_domain_nameservers against Cloudflare zone data to audit whether nameserver assignments in Markmonitor match what Cloudflare is actually authoritative for. This kind of cross-source query is exactly what CloudQuery's data layer is built for.

Getting Started #

The integration requires an API key, username, and password from your Markmonitor account. Contact Markmonitor support if you need to generate an API key.

kind: source
spec:
  name: markmonitor
  path: cloudquery/markmonitor
  registry: cloudquery
  version: 'v1.0.1'
  tables: ['*']
  destinations: ['postgresql']
  spec:
    api_key: '${MARKMONITOR_API_KEY}'
    username: '${MARKMONITOR_USERNAME}'
    password: '${MARKMONITOR_PASSWORD}'

This is a premium integration. See the full documentation for setup details.

Start Syncing Your Domain Portfolio

See how Markmonitor data fits alongside your cloud infrastructure in CloudQuery. Check out the Markmonitor integration docs or browse all available integrations.

Schedule a Demo

Frequently Asked Questions #

What is the Markmonitor CloudQuery integration? It's a source integration that syncs domain data from Markmonitor - including domain details, DNSSEC configuration, and nameserver assignments - into any CloudQuery-supported destination like PostgreSQL, BigQuery, or Snowflake.

What tables does the integration provide? Three tables: markmonitor_domain_details (domain inventory and expiration dates), markmonitor_domain_dnssec (DNSSEC configuration), and markmonitor_domain_nameservers (nameserver assignments per domain).

Who should use this integration? Teams managing enterprise domain portfolios through Markmonitor who want SQL-accessible visibility into domain expiration, DNS security posture, and nameserver configuration - alongside the rest of their cloud infrastructure data. If you use a different registrar, check out the Gandi integration as well.

Can I combine Markmonitor data with other CloudQuery integrations? Yes. Cross-referencing markmonitor_domain_details and markmonitor_domain_nameservers against AWS Route 53 or Cloudflare zone data is a common use case for finding orphaned registrations or nameserver drift.

What destinations does it support? Any CloudQuery destination: PostgreSQL, BigQuery, Snowflake, and more. See the CloudQuery Hub for the full list.

Is this a premium integration? Yes. Reach out via the contact form above or contact us to get access.

CloudOps