☰

seedtag.com

IP address 104.16.56.62
DNS managed by Cloudflare
Mail Configured
Records 24

The domain seedtag.com answers at IP address 104.16.56.62. The domain DNS is managed by Cloudflare, which decides where each subdomain points. Mail for seedtag.com goes through 5 servers; the highest priority one is aspmx.l.google.com. It also publishes 14 TXT records, used to verify domain ownership with external services and to configure mail security through SPF, DKIM and DMARC.

A A records

MX MX records

NS NS records

TXT TXT records

  • slack-domain-verification=do7v6UhCwmKxC3DXr3ZSd5fjq7Wpm9NLQ0UYRlwQ 300s
  • 31a787a4729d53adb49e179f3efe9c79 300s
  • google-site-verification=pRqinvMQH3m1zrBJbwebmO-xrUFtMtjR0sWckKkBbp0 300s
  • anthropic-domain-verification-xk4dzr=mxHmrdYVeCjxwgoHTg8bjEHvO 300s
  • google-site-verification=mwc46tDU758P8elNFJmuIif9brwYqDyWUd212_x5SCk 300s
  • apple-domain-verification=HOmddmXuw5VIitJe 300s
  • atlassian-domain-verification=L5WTBuKMXCHQu5aesBbjc97CKKq5W5v8EvaQDw0KpMfUCaABNQGXgFJ4H22KYygM 300s
  • google-site-verification=lfS9pByKc7ta1pl4s9dcnaucQ4aJA-7ak3p4QusBbf4 300s
  • amazonses:dir6752ci7Z+Pf3NOSEvOu5M8ebmw+ug34sJZv232vY= 300s
  • google-site-verification=XqzGNmV9c35kPI7P_dDjccvY6JozR6zaXRD3ZzkSgKs 300s
  • MS=02E6DFB10DD64910382479E2BB403C35CEAF2FF6 300s
  • v=spf1 include:_spf.google.com include:mailgun.org include:servers.mcsv.net include:_spf.salesforce.com include:amazonses.com include:19567840.spf04.hubspotemail.net include:00d7q000008lzoa=1tbtt000000052w ~all 300s
  • google-site-verification=Kyaw_NmPgPA0g3UXwzmucljOECn9yI4w8aY2EtY4Pig 300s
  • atlassian-sending-domain-verification=513ab098-9382-45a4-8724-e40d53c202ed 300s

SOA SOA records

  • gabe.ns.cloudflare.com 1800s

What each record means

  • A and AAAA: the server IP address, in IPv4 and IPv6.
  • MX: the servers that receive the domain mail. The number is the priority; the lowest is tried first.
  • NS: the name servers, which have the final say over the domain DNS.
  • TXT: free text. Mostly used for SPF, DKIM and DMARC, and to verify ownership with third parties.
  • TTL: how many seconds the record may be cached before asking again.

Checked 3 hours ago.