DNS Lookup

A, AAAA, MX, NS, TXT, SOA and CAA records.

Records for cyrusone.com

Type TTL Value
A 3433s 199.60.103.169
A 3433s 199.60.103.69
MX 3600s priority=10 us-smtp-inbound-2.mimecast.com
MX 3600s priority=10 us-smtp-inbound-1.mimecast.com
NS 86233s dns4.cyrusone.com
NS 86233s dns1.cyrusone.com
NS 86233s dns2.cyrusone.com
NS 86233s dns3.cyrusone.com
TXT 3600s jamf-site-verification=7wQwe8lfHsxGv_5R49Nevw
TXT 3600s v=spf1 include:us._netblocks.mimecast.com include:spf.protection.outlook.com include:_spf.salesforce.com include:asp-spf1.yardi.com include:asp-spf2.yardi.com include:spf.us1.defend.egress.com ip4:216.117.89.100 ip4:216.117.89.101 ip4:192.254.125.211 ip4:216.244.113.55 ip4:208.185.229.0/24 ip4:208.185.235.0/24 ip4:148.59.108.0/23 ip4:148.59.106.0/23 ip4:103.28.42.0/24 ip4:146.88.28.0/24 ip4:203.55.21.0/24 ip4:204.75.142.0/24 ip4:167.89.106.151 a:b.spf.service-now.com a:c.spf.service-now.com a:d.spf.service-now.com include:servers.mcsv.net ip4:3.93.157.0/24 ip4:3.210.190.0/24 ip4:18.208.124.128/25 ip4:54.174.52.0/24 ip4:54.174.53.128/30 ip4:54.174.57.0/24 ip4:54.174.59.0/24 ip4:54.174.60.0/23 ip4:54.174.63.0/24 ip4:139.180.17.0/24 ip4:143.244.80.0/20 ip4:158.247.16.0/20 ~all
TXT 3600s atlassian-domain-verification=9adAqHrkAPLIw5cdEQxKnzcFpsz/smkMPMgnbAKcQkoSHyn3RHoZs7pdwQ4ZoKTY
TXT 3600s google-gws-recovery-domain-verification=61327064
TXT 3600s 0ed1fe018a6b32c778a5b04fa6ab83b95b59f7223c
TXT 3600s teamviewer-sso-verification=de88b3c6935740eda2d799db57f06479
TXT 3600s google-site-verification=ZjFPRpLAA8HwxbtatEgL5j3emGsbtvbdZqFNnJwt4XI
TXT 3600s MS=ms89500588
TXT 3600s google-site-verification=JVt_IJpI88iUI4EfmlQhxBu1p_9liiZCQzAj3et_ssc
TXT 3600s openai-domain-verification=dv-oDdfp6zfxtQkm2Xps41E2Ocv
TXT 3600s docusign=eeef520c-1c76-47bf-91af-a7dc9c4204ec
TXT 3600s anthropic-domain-verification-e95573=wtPyNSTd8Aaks7LjP5C91UNch
TXT 3600s miro-verification=a1706fa17a5a0baee9ac37dfb74f97ca968bb71a
TXT 3600s v=DMARC1; p=none; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com;fo=1
TXT 3600s FfvsQEqHw2dazXJOrPrRfhVpevbR7MsOGmo0H+dEGX0ntaTgD2xp7F+BIqyAXVTozAmS3Vj7YtJ1NDAdj2QlZg==
TXT 3600s apple-domain-verification=A5ibADYxmOmEkW9C
SOA 43157s mname=dns1.cyrusone.com rname=support.cyrusone.com serial=2016030580

About DNS Lookup

This DNS lookup queries every common record type in one pass: A and AAAA for IPv4 and IPv6 addresses, MX for mail servers, NS for the authoritative nameservers, TXT for verification strings and SPF, SOA for the zone start of authority, CAA for certificate authority restrictions, and CNAME aliases. Each record returns with its time-to-live so you can see how long resolvers will cache the answer.

When to use it

Check this tool right after changing DNS at your registrar to confirm the new records are visible from the public resolver chain. Use it to compare what a candidate hosting provider's nameservers return versus your current setup. Sysadmins also rely on it to verify CAA records before issuing a new TLS certificate, since a misconfigured CAA can block Let's Encrypt and other CAs from issuing.

How to read the results

TTL values in seconds tell you how long a change will take to propagate after you reduce it. A records hold IPv4 addresses, AAAA holds IPv6. MX records show priority then target, lowest priority wins. NS records list the authoritative nameservers, which should match what your registrar shows. A missing CAA record means any public CA can issue certificates, which is often fine but worth knowing.

Frequently asked questions

Why do I see multiple A records for one hostname?

Multiple A records mean DNS round-robin. The resolver picks one each query, spreading traffic across the listed IPs. Large sites combine this with anycast for redundancy and load distribution across regions.

What is the difference between an A and a CNAME record?

An A record points directly to an IP address. A CNAME points to another hostname, which then resolves to an A record. CNAMEs cannot coexist with other records on the same name, including the apex.

How long until my DNS changes show up here?

It depends on the TTL of the previous record. If the old TTL was 3600 seconds, expect up to an hour for caches to flush. New records with a low TTL appear quickly once the authoritative server returns them.

What does the SOA record tell me?

The Start of Authority record holds the primary nameserver for the zone, the admin contact email (with dots instead of @), serial number, refresh and retry intervals, and minimum TTL. The serial increments on every zone change.

Who Is Online

In total there are 76 users online: 0 registered, 69 guests and 7 bots.

Bots: AhrefsBot Applebot Bingbot Facebook Other Bot Other Spider SemrushBot

Users active in the past 15 minutes. Total registered members: 340