buzzvil.com
The domain buzzvil.com answers at IP address 76.76.21.21. That address belongs to Vercel, Inc, based in United States. The domain DNS is managed by Amazon Route 53, which decides where each subdomain points. Mail for buzzvil.com goes through 5 servers; the highest priority one is aspmx.l.google.com. It also publishes 11 TXT records, used to verify domain ownership with external services and to configure mail security through SPF, DKIM and DMARC.
A A records
- 76.76.21.21 300s
MX MX records
- 1 aspmx.l.google.com 300s
- 5 alt2.aspmx.l.google.com 300s
- 5 alt1.aspmx.l.google.com 300s
- 10 alt4.aspmx.l.google.com 300s
- 10 alt3.aspmx.l.google.com 300s
NS NS records
- ns-197.awsdns-24.com 21600s
- ns-917.awsdns-50.net 21600s
- ns-1749.awsdns-26.co.uk 21600s
- ns-1222.awsdns-24.org 21600s
TXT TXT records
- MS=3981C18C93BA57D30AD49ABEA43775032AFA3E96 300s
- google-site-verification=7jKzqqfYY6dKRPSJgOKLfW0i92xHxkw7143QfTxz1dA 300s
- sn3ctxd4zbrw00yzh243qpl4llptfb1r 300s
- google-site-verification=zLtcESFLqyWUNYi27MC3zZ4N3JrNAzZwAv30pZKBqAI 300s
- v=spf1 include:aspmx.pardot.com include:_spf.google.com include:mail.stibee.com include:_spf.salesforce.com ~all 300s
- google-site-verification=nY32ES31wyYCytRwxKKWl_VFeXd-g9hicQcykgGzi_s 300s
- google-site-verification=jYTGKgBD2yJwEYOn-y1lLh9cq8AIHRhdKDSw8Rkhm_Q 300s
- google-site-verification=AklNqPdeftALF2xxESqVrZkvnezX9S8DzVNxwOdZ930 300s
- google-site-verification=4Ni1R25-S73PsZTWANOxljCg8Brzept2urHzXBjeiWY 300s
- anthropic-domain-verification-9nygw0=hxsMtk8b0liacA9Ugeb3g8AZy 300s
- pardot848113=e92e63c177f49a4b66e44ec487ecfd5e13e50df1fe9636ade367df72e78b3832 300s
SOA SOA records
- ns-1222.awsdns-24.org 900s
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.