☰

duosecurity.com

IP address 13.35.58.95
DNS managed by Amazon Route 53
Mail Configured
Records 26

The domain duosecurity.com answers at IP address 13.35.58.95. The domain DNS is managed by Amazon Route 53, which decides where each subdomain points. Mail for duosecurity.com goes through 3 servers; the highest priority one is alln-mx-01.cisco.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

  • _vz1bepjjh5vfz1kdz31jma6hzwg20ny 300s
  • google-site-verification=HmBniYqxTjdE-G67pjqWN0Z92oVYeLYB0pRpBUAJ1sE 300s
  • v=spf1 include:_spf.duosecurity.com include:_spf2.duosecurity.com include:_spf.google.com include:mktomail.com exists:%{i}._spf.mta.salesforce.com include:mail.zendesk.com include:spf.bananatag.com ~all 300s
  • cisco-ci-domain-verification=5e3a213be18d8a0d35b53e7efed6be85c8f44493f253d7cc7ceb030ae9ddc2a4 300s
  • atlassian-domain-verification=R4UtYgXtORXRKnMUBQS0AFJD3EAxj2HTgORPt6C1/GLPaTOI7alUkMvuq/3ABby8 300s
  • ygl4n9zvmlf74mcbbc8nmcr3wv915q7g 300s
  • duo_sso_verification=kuyK6IAuOS7ombaHhSEWM0gFk2Ja0oUHefceWQT7z4uU8rWqw8DjuTsUtmdRT6xd 300s
  • z5c69y4b0q179syyqltskhhsrtndrx6m 300s
  • hcp-domain-verification=2864ca4b8eab48057506880821e0203db32c5c2c09a71425ae6d5a1dfe8cb22c 300s
  • apple-domain-verification=2Vf56S4tuuskojVe 300s
  • status-page-domain-verification=wl6tj66k5qh5 300s
  • MS=ms87573650 300s
  • google-site-verification=zlwiWUyTXIR20h2du1EFVF_9W6mlgspR2iwUHOGbz6Q 300s
  • _k6higb2z1hho56o41tneh9qzuuezz9o 300s

SOA SOA records

  • ns-1600.awsdns-08.co.uk 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.