ozalert.com - robtex.com
ozalert.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.netregistry.net ⚠️ Not in zone NS records | ||||||
| A | 13.248.158.180🇺🇸 Amazon13.248.144.0/20 | ||||||
| PTR | a79764cc55c0ac9c0.awsglobalaccelerator.com | ||||||
| NS | ns2.netregistry.net ⚠️ Not in zone NS records | ||||||
| A | 75.2.118.134🇺🇸 Amazon75.2.112.0/20 | ||||||
| PTR | abc65dd9a44b5332f.awsglobalaccelerator.com | ||||||
| NS | ns3.netregistry.net ⚠️ Not in zone NS records | ||||||
| A | 76.223.26.245🇺🇸 Amazon76.223.16.0/20 | ||||||
| PTR | a79764cc55c0ac9c0.awsglobalaccelerator.com | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1774551477 | ||||||
Same first word
ozalert.com |
Similar names
DNS History
18 records (3 active, 15 former)
○NSdns1.namesecure.com2008-03-17 → 2008-03-17 · 3 obs
● 2008-03-17 09:35:54
○ 2015-07-05 02:33:58
○ 2026-03-26 19:26:16
○ 2015-07-05 02:33:58
○ 2026-03-26 19:26:16
○NSdns2.namesecure.com2008-03-17 → 2008-03-17 · 3 obs
● 2008-03-17 09:35:54
○ 2015-07-05 02:33:58
○ 2026-03-26 19:26:16
○ 2015-07-05 02:33:58
○ 2026-03-26 19:26:16
○NSns1.auserver.com.au2015-07-05 → 2016-07-09 · 5 obs
○ 2008-03-17 09:35:54
● 2015-07-05 02:33:58
● 2016-07-09 08:43:08
○ 2017-03-22 12:16:04
○ 2026-03-26 19:26:16
● 2015-07-05 02:33:58
● 2016-07-09 08:43:08
○ 2017-03-22 12:16:04
○ 2026-03-26 19:26:16
●NSns1.netregistry.net2026-03-26 → 2026-03-26 · 2 obs
○ 2020-03-10 02:43:04
● 2026-03-26 19:26:16
● 2026-03-26 19:26:16
○NSns15.domaincontrol.com2020-03-10 → 2020-03-10 · 3 obs
○ 2017-03-22 12:16:04
● 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
● 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
○NSns16.domaincontrol.com2020-03-10 → 2020-03-10 · 3 obs
○ 2017-03-22 12:16:04
● 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
● 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
○NSns2.auserver.com.au2015-07-05 → 2016-07-09 · 5 obs
○ 2008-03-17 09:35:54
● 2015-07-05 02:33:58
● 2016-07-09 08:43:08
○ 2017-03-22 12:16:04
○ 2026-03-26 19:26:16
● 2015-07-05 02:33:58
● 2016-07-09 08:43:08
○ 2017-03-22 12:16:04
○ 2026-03-26 19:26:16
●NSns2.netregistry.net2026-03-26 → 2026-03-26 · 2 obs
○ 2020-03-10 02:43:04
● 2026-03-26 19:26:16
● 2026-03-26 19:26:16
●NSns3.netregistry.net2026-03-26 → 2026-03-26 · 2 obs
○ 2020-03-10 02:43:04
● 2026-03-26 19:26:16
● 2026-03-26 19:26:16
○NSns49.domaincontrol.com2017-03-22 → 2017-03-22 · 4 obs
○ 2016-07-09 08:43:08
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
○NSns50.domaincontrol.com2017-03-22 → 2017-03-22 · 4 obs
○ 2016-07-09 08:43:08
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
○MXmail.ozalert.com2015-07-05 → 2016-07-09 · 5 obs
○ 2008-03-17 09:35:54
● 2015-07-05 02:33:58
● 2016-07-09 08:43:08
○ 2017-03-22 12:16:04
○ 2026-03-26 19:26:16
● 2015-07-05 02:33:58
● 2016-07-09 08:43:08
○ 2017-03-22 12:16:04
○ 2026-03-26 19:26:16
○MXmailstore1.secureserver.net2017-03-22 → 2017-03-22 · 4 obs
○ 2016-07-09 08:43:08
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
○MXsmtp.secureserver.net2017-03-22 → 2017-03-22 · 4 obs
○ 2016-07-09 08:43:08
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
○A101.0.116.552015-07-05 → 2016-07-09 · 5 obs
○ 2008-03-17 09:35:54
● 2015-07-05 02:33:58
● 2016-07-09 08:43:08
○ 2017-03-22 12:16:04
○ 2026-03-26 19:26:16
● 2015-07-05 02:33:58
● 2016-07-09 08:43:08
○ 2017-03-22 12:16:04
○ 2026-03-26 19:26:16
○A184.168.221.372020-03-10 → 2020-03-10 · 3 obs
○ 2017-03-22 12:16:04
● 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
● 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
○A209.62.21.2152008-03-17 → 2008-03-17 · 3 obs
● 2008-03-17 09:35:54
○ 2015-07-05 02:33:58
○ 2026-03-26 19:26:16
○ 2015-07-05 02:33:58
○ 2026-03-26 19:26:16
○A45.248.84.522017-03-22 → 2017-03-22 · 4 obs
○ 2016-07-09 08:43:08
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| ozalert.com | ns3.netregistry.net, ns1.netregistry.net, ns2.netregistry.net | - |
✅ Authoritative Response
Server:13.248.158.180
NS records: ns3.netregistry.net, ns1.netregistry.net, ns2.netregistry.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ozalert.com (unsigned zone)
⏱️ Timing
Total: 182ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
The domain ozalert.com is delegated to three name servers: ns1.netregistry.net, ns2.netregistry.net and ns3.netregistry.net.
ozalert.com shares name servers with other domains at least partially, for instance mintatown.com.au, 123home.net.au, ambianztech.com, pestoff.com.au and waterfordcounty.com.au.
these name servers are commonly used together with ns1.planetdomain.com and ns2.planetdomain.com.
Host names with a single IP number:
ns1.netregistry.net points to 13.248.158.180.
ns2.netregistry.net points to 75.2.118.134.
ns3.netregistry.net points to 76.223.26.245.