ozalert.com - dns.ninja
ozalert.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=1785576217 | ||||||
MX for
ozalert.com |
Same first word
ozalert.com |
Similar names
DNS History
24 records (9 active, 15 former)
○NSdns1.namesecure.com2008-03-17 → 2008-03-17 · 3 obs
○ 2015-07-05 02:33:58
○ 2026-08-01 09:31:16
○NSdns2.namesecure.com2008-03-17 → 2008-03-17 · 3 obs
○ 2015-07-05 02:33:58
○ 2026-08-01 09:31:16
○NSns1.auserver.com.au2015-07-05 → 2016-07-09 · 5 obs
● 2015-07-05 02:33:58
● 2016-07-09 08:43:08
○ 2017-03-22 12:16:04
○ 2026-08-01 09:31:16
●NSns1.mysecurecloudhost.com2026-05-15 → 2026-08-01 · 3 obs
● 2026-05-15 06:44:38
● 2026-08-01 09:31:16
●NSns1.netregistry.net2026-03-26 → 2026-08-01 · 3 obs
● 2026-03-26 19:26:16
● 2026-08-01 09:31:16
○NSns15.domaincontrol.com2020-03-10 → 2020-03-10 · 4 obs
● 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
○ 2026-08-01 09:31:16
○NSns16.domaincontrol.com2020-03-10 → 2020-03-10 · 4 obs
● 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
○ 2026-08-01 09:31:16
○NSns2.auserver.com.au2015-07-05 → 2016-07-09 · 5 obs
● 2015-07-05 02:33:58
● 2016-07-09 08:43:08
○ 2017-03-22 12:16:04
○ 2026-08-01 09:31:16
●NSns2.mysecurecloudhost.com2026-05-15 → 2026-08-01 · 3 obs
● 2026-05-15 06:44:38
● 2026-08-01 09:31:16
●NSns2.netregistry.net2026-03-26 → 2026-08-01 · 3 obs
● 2026-03-26 19:26:16
● 2026-08-01 09:31:16
●NSns3.mysecurecloudhost.com2026-05-15 → 2026-08-01 · 3 obs
● 2026-05-15 06:44:38
● 2026-08-01 09:31:16
●NSns3.netregistry.net2026-03-26 → 2026-08-01 · 3 obs
● 2026-03-26 19:26:16
● 2026-08-01 09:31:16
●NSns4.mysecurecloudhost.com2026-05-15 → 2026-08-01 · 3 obs
● 2026-05-15 06:44:38
● 2026-08-01 09:31:16
○NSns49.domaincontrol.com2017-03-22 → 2017-03-22 · 4 obs
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-08-01 09:31:16
○NSns50.domaincontrol.com2017-03-22 → 2017-03-22 · 4 obs
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-08-01 09:31:16
○MXmail.ozalert.com2015-07-05 → 2016-07-09 · 5 obs
● 2015-07-05 02:33:58
● 2016-07-09 08:43:08
○ 2017-03-22 12:16:04
○ 2026-08-01 09:31:16
○MXmailstore1.secureserver.net2017-03-22 → 2017-03-22 · 4 obs
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-08-01 09:31:16
●MXozalert.com2026-05-15 → 2026-08-01 · 3 obs
● 2026-05-15 06:44:38
● 2026-08-01 09:31:16
○MXsmtp.secureserver.net2017-03-22 → 2017-03-22 · 4 obs
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-08-01 09:31:16
○A101.0.116.552015-07-05 → 2016-07-09 · 5 obs
● 2015-07-05 02:33:58
● 2016-07-09 08:43:08
○ 2017-03-22 12:16:04
○ 2026-08-01 09:31:16
●A178.128.175.142026-05-15 → 2026-08-01 · 3 obs
● 2026-05-15 06:44:38
● 2026-08-01 09:31:16
○A184.168.221.372020-03-10 → 2020-03-10 · 4 obs
● 2020-03-10 02:43:04
○ 2026-03-26 19:26:16
○ 2026-08-01 09:31:16
○A209.62.21.2152008-03-17 → 2008-03-17 · 3 obs
○ 2015-07-05 02:33:58
○ 2026-08-01 09:31:16
○A45.248.84.522017-03-22 → 2017-03-22 · 4 obs
● 2017-03-22 12:16:04
○ 2020-03-10 02:43:04
○ 2026-08-01 09:31: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:75.2.118.134
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: 855ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 178.128.175.14 |
| NS | 4 | ns2.mysecurecloudhost.com, ns4.mysecurecloudhost.com... |
| MX | 1 | ozalert.com (pri: 0) |
| TXT | 1 | v=spf1 +a +mx +ip4:69.72.248.157 include |
| SOA | 1 | ns1.mysecurecloudhost.com rbt\.dale.gmai |
Analysis
Mail Server Role
The MX record for ozalert.com points back to ozalert.com — it is its own mail server.
IP Addresses
ozalert.com directs to one IP number, which is 178.128.175.14.
Among the host names that share IP numbers with ozalert.com are mail.congressofchristianleadership.com, mail.inplacetech.com, desibag.com and two others.
Name Servers
ozalert.com is delegated to 7 name servers: ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com and 4 other.
There is at least partial name server overlap between ozalert.com and other domains — training-institution.com, docsspot.com, mongolfierefirenze.com and two more among them.
These name servers regularly appear alongside ns4.mysecurecloudhost.com, ns1.netregistry.net, ns2.netregistry.net and 5 other name servers in NS record sets.
Hosts that resolve to one IP address:
ns1.mysecurecloudhost.com points to 13.248.158.180.
ns2.mysecurecloudhost.com points to 75.2.118.134.
ns3.mysecurecloudhost.com points to 76.223.26.245.
ns4.mysecurecloudhost.com points to 99.83.147.209.
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.
ns1.mysecurecloudhost.com and ns1.netregistry.net are host names that each point to 13.248.158.180 IP addresses.
ns2.mysecurecloudhost.com and ns2.netregistry.net are host names that each point to 75.2.118.134 IP addresses.
ns3.mysecurecloudhost.com and ns3.netregistry.net are host names that each point to 76.223.26.245 IP addresses.
Mail Servers
The MX record for ozalert.com points to a single mail server: ozalert.com.
ozalert.com resolves to a single IP number: 178.128.175.14.