zigzag.kr: IP address, DNS records and WHOIS
Live lookup data for zigzag.kr: 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
| 13.224.95.31 | TTL 60 |
| 13.224.95.59 | TTL 60 |
| 13.224.95.54 | TTL 60 |
| 13.224.95.25 | TTL 60 |
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 |
| aspmx2.googlemail.com | 10 |
| aspmx3.googlemail.com | 10 |
NS
| ns-1007.awsdns-61.net |
| ns-1328.awsdns-38.org |
| ns-1675.awsdns-17.co.uk |
| ns-94.awsdns-11.com |
TXT
| google-site-verification=KOk0UjdSQtobBDe-vwuSHLyIzrXD3Ij2wwtGR0H6Lcc |
| v=spf1 include:amazonses.com include:mail.stibee.com ~all |
SOA
- Primary nameserver
- ns-94.awsdns-11.com
- 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
No public records of this type are currently published.
WHOIS registration data
- Registered
- Apr 6, 2010
- Expires
- Apr 6, 2029
- Last changed
- Apr 5, 2024
- Status
- client delete prohibited, client transfer prohibited, client update prohibited
- Nameservers
- ns-1007.awsdns-61.net, ns-1328.awsdns-38.org, ns-1675.awsdns-17.co.uk, ns-94.awsdns-11.com
- DNSSEC signed
- No
FAQ
zigzag.kr currently resolves to 13.224.95.31, 13.224.95.59, 13.224.95.54, 13.224.95.25. Large sites often publish several addresses and rotate them, so the list can differ between checks and between locations.
zigzag.kr is registered through its registrar. The registrant's identity is not published in the public registration record — most owners use a privacy service or the data is redacted.
zigzag.kr is served by ns-1007.awsdns-61.net, ns-1328.awsdns-38.org, ns-1675.awsdns-17.co.uk, ns-94.awsdns-11.com. 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: