meraki.com
The domain meraki.com answers at IP address 18.245.86.31. The domain DNS is managed by Amazon Route 53, which decides where each subdomain points. Mail for meraki.com goes through 3 servers; the highest priority one is alln-mx-01.cisco.com. It also publishes 12 TXT records, used to verify domain ownership with external services and to configure mail security through SPF, DKIM and DMARC.
A A records
- 18.245.86.31 60s
- 18.245.86.39 60s
- 18.245.86.14 60s
- 18.245.86.104 60s
MX MX records
- 10 alln-mx-01.cisco.com 101s
- 20 rcdn-mx-01.cisco.com 101s
- 30 aer-mx-01.cisco.com 101s
NS NS records
- ns-1777.awsdns-30.co.uk 19577s
- ns-112.awsdns-14.com 19577s
- ns-855.awsdns-42.net 19577s
- ns-1423.awsdns-49.org 19577s
TXT TXT records
- wrike-verification=MjEzNzM3NjpmNGM0ZGMzZjcxMzYyNmE4NjM3ZTNiMjA1NTgxNmNiNjc4YWVhNjc3ZWIxNzc2M2YxYjc5MDBlNmM4ZDIxYzg4 300s
- MS=ms78214898 300s
- identrust_validate=LZdS0KuNmDCqbXaWYVvB8j8fvWQhIliA2n+ohW5C/7Qi 300s
- adobe-idp-site-verification=c08578d97fc1bb012e79e6bc3c29f7d6458670b636bf1143a707679887e317b0 300s
- fktlhibfsv149gibvln6ipf45h 300s
- postman-domain-verification=8dcd461c89102c435b68ccaac00f9758d15c5fa3d88f54679a46ee9c32e5d98b50536aa507edf13be93d9665509b63e518cebc4dd4c64bd44bf9fef93759b843 300s
- uf84s1envst5gcn4vifmkrl5kd 300s
- miro-verification=53bf5ccd47cb6239fe5cf14c3b328050dd5679ac 300s
- identrust_validate=3c7tQF7jrx2Z6giVD0XW41AHdN4aSRuGJWVcLrBQb0z5 300s
- google-site-verification=h020xCrrhiNgm86-ntglLTvnI_wNWgRHO036eF7zKLc 300s
- v=spf1 include:amazonses.com include:_spf.google.com include:_spf.salesforce.com include:us.khoros-mail.com include:mail.zendesk.com include:mktomail.com ~all 300s
- d1x0alisu9v9bg.cloudfront.net 300s
SOA SOA records
- ns-1777.awsdns-30.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 4 hours ago.