npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

verify-domain

v1.1.0

Published

Verify domain ownership using DNS or HTTP easily in Node.js

Downloads

5

Readme

verify-domain

verify-domain allows you to verify whether someone owns a domain name or a subdomain. It can do this in two ways:

  • DNS (recommended): This checks whether or not a TXT record is present on a subdomain with a generated key.
  • HTTP: This checks whether a generated key is present in a text file on the domain.

Install

[!NOTE]
verify-domain requires Node.js 17 or higher to work.

You can install verify-domain via npm or your favourite package manager.

npm install verify-domain

Verify using DNS

You can easily verify using a TXT DNS record on _name.domain.invalid, with name being the name you provided. This is the recommended way of verifying a domain. verify-domain handles all queries and key generation for you.

const { getKey, verifyUsingDNS } = require("verify-domain");

// name should be your application name or something similar
const { match, domain } = await getKey("domain.invalid", "name");
console.log(`You need to enter '${match}' as a TXT record into ${domain}`);

try {
  await verifyUsingDNS("domain.invalid", "name");
  console.log("Verified!");
} catch (err) {
  console.error(err);
}

Verify using HTTP

You can also verify using HTTP(S) by letting users add a text file to http://domain.invalid/.well-known/name, with name being the name you provided.

const { getKey, verifyUsingHTTP } = require("verify-domain");

// name should be your application name or something similar
const { match, url } = await getKey("domain.invalid", "name");
console.log(`You need to have a file with '${match}' at ${url}`);

try {
  await verifyUsingHTTP("domain.invalid", "name");
  console.log("Verified!");
} catch (err) {
  console.error(err);
}

Usage with AbortController

You can also pass in a AbortSignal to the options when verifying. This allows you to cancel the verification process as you desire, like after a certain amount of time.

For DNS verification, a custom DNSVerifyAbortError will be thrown (which can be imported). For HTTP verification, a DOMException (Node.js global) will be thrown. In both cases, you can check that error.name is AbortError.

const { verifyUsingHTTP } = require("verify-domain");

const controller = new AbortController();
const timeout = setTimeout(() => controller.abort(), 5_000); // Abort after 5 seconds

try {
  await verifyUsingHTTP("domain.invalid", "name", { signal: controller.signal });
  console.log("Verified!");
} catch (error) {
  if (error.name === "AbortError") {
    console.error("Verification timed out!");
  } else {
    console.error(error);
  }
}

clearTimeout(timeout);