split.io: IP address, DNS records and WHOIS
Live lookup data for split.io: the IP addresses it resolves to, the DNS records it publishes, and its registration details. The data below is fetched when this page is built and refreshed daily.
At a glance
DNS records
A
| 198.202.211.1 | TTL 193 |
AAAA
No public records of this type are currently published.
CNAME
No public records of this type are currently published.
MX
| aspmx.l.google.com | 1 |
| alt1.aspmx.l.google.com | 5 |
| alt2.aspmx.l.google.com | 5 |
| alt3.aspmx.l.google.com | 10 |
| alt4.aspmx.l.google.com | 10 |
NS
| ns-1183.awsdns-19.org |
| ns-1842.awsdns-38.co.uk |
| ns-335.awsdns-41.com |
| ns-877.awsdns-45.net |
TXT
| MS=ms12528989 |
| status-page-domain-verification=t5t853dqw02d |
| docusign=9cf5c10a-fbc1-4998-96a1-48041624fa9c |
| v=zoomadn us.zoom.idp.commercial=split.okta.com |
| airtable-verification=0fcab18bdc80e27e22a5549940856b30 |
| miro-verification=76692e6e01f3df4899ec315d00829e1c2adc75d7 |
| mongodb-site-verification=k01K9YKEIW8X4F60JO4ErFKfCcgZqH0R |
| slack-domain-verification=oEpbXlA1eOsQik2EBXaPWG4We4LWpetnTXROwEyy |
SOA
- Primary nameserver
- ns-877.awsdns-45.net
- Hostmaster
- awsdns-hostmaster@amazon.com
- Serial
- 1
- Refresh
- 7200 s (2 hours)
- Retry
- 900 s (15 minutes)
- Expire
- 1209600 s (14 days)
- Minimum TTL
- 86400 s (1 day)
CAA
| 0 iodef "mailto:infra@split.io" |
| 0 issue "amazon.com" |
| 0 issue "amazonaws.com" |
| 0 issue "amazontrust.com" |
| 0 issue "aws.amazon.com" |
| 0 issue "awstrust.com" |
| 0 issue "digicert.com" |
| 0 issue "globalsign.com" |
| 0 issue "letsencrypt.org" |
WHOIS registration data
No public RDAP registration record is published for this domain, so registration details cannot be shown.
FAQ
split.io currently resolves to 198.202.211.1. Large sites often publish several addresses and rotate them, so the list can differ between checks and between locations.
split.io is served by ns-1183.awsdns-19.org, ns-1842.awsdns-38.co.uk, ns-335.awsdns-41.com, ns-877.awsdns-45.net. These are the authoritative nameservers that publish its DNS records.
Run a fresh check
Records change. Run the live tools for an up-to-the-minute answer: