gets.co.za - robtex.com
gets.co.za
co.za
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns.coza.net.za ⭐ | ||||||
| NS | coza1.dnsnode.net | ||||||
| NS | ns2.dns.net.za | ||||||
| NS | ns2us.dns.business | ||||||
| NS | ns5.dns.net.za | ||||||
| MX | mx2.dns.business ⭐ | ||||||
| TXT | google-site-verification=likJ1inLA3BiWH30vLTURD5kbYZshPreaO0bQH_pMVM | ||||||
| TXT | v=spf1 a:mail.coza.net.za a:mx2.coza.net.za a:mail.registry.net.za include:_... | ||||||
| SOA | ns.coza.net.zathis-is-probably-not-the-email-address-you-are-looking-for@co.za serial=2025077280 | ||||||
rank #1315 in the tld
WOT: SAFE (72/100)
Same first word
Similar names
DNS History
12 records (10 active, 2 former)
●NSns1.host-ww.net2026-06-17 → 2026-07-04 · 3 obs
● 2026-06-17 16:18:24
● 2026-07-04 19:44:10
●NSns1.speedy-dns.com2015-06-10 → 2026-07-04 · 2 obs
● 2026-07-04 19:44:10
●NSns2.host-ww.net2026-06-17 → 2026-07-04 · 3 obs
● 2026-06-17 16:18:24
● 2026-07-04 19:44:10
●NSns2.speedy-dns.com2015-06-10 → 2026-07-04 · 2 obs
● 2026-07-04 19:44:10
●MXalt1.aspmx.l.google.com2015-06-10 → 2026-07-04 · 2 obs
● 2026-07-04 19:44:10
●MXalt2.aspmx.l.google.com2015-06-10 → 2026-07-04 · 2 obs
● 2026-07-04 19:44:10
●MXaspmx.l.google.com2015-06-10 → 2026-07-04 · 2 obs
● 2026-07-04 19:44:10
●MXaspmx2.googlemail.com2015-06-10 → 2026-07-04 · 2 obs
● 2026-07-04 19:44:10
●MXaspmx3.googlemail.com2015-06-10 → 2026-07-04 · 2 obs
● 2026-07-04 19:44:10
●A102.130.122.1562026-06-17 → 2026-07-04 · 3 obs
● 2026-06-17 16:18:24
● 2026-07-04 19:44:10
○A138.201.19.42016-04-20 → 2016-12-23 · 5 obs
● 2016-04-20 07:13:02
● 2016-12-23 04:40:28
○ 2026-06-17 16:18:24
○ 2026-07-04 19:44:10
○A178.63.20.202015-06-10 → 2016-01-19 · 4 obs
● 2016-01-19 23:35:06
○ 2016-04-20 07:13:02
○ 2026-07-04 19:44:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| za | za1.dnsnode.net, nsza.is.co.za, za-ns.anycast.pch.net | 5 records |
| gets.co.za | ns2.host-ww.net, ns1.host-ww.net | - |
✅ Authoritative Response
Server:169.239.180.4
NS records: ns2.host-ww.net, ns1.host-ww.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for gets.co.za (unsigned zone)
⏱️ Timing
Total: 2250ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 102.130.122.156 |
| NS | 2 | ns2.speedy-dns.com, ns1.speedy-dns.com |
| MX | 5 | aspmx.l.google.com (pri: 0), aspmx2.googlemail.com (pri: 10)... |
| TXT | 1 | v=spf1 +a +mx +ip4:102.130.122.156 inclu |
| SOA | 1 | ns1.speedy-dns.com admin.digiserv.biz |
📌 Glue Records Collected
Total: 5
In-bailiwick: 1 (nsza.is.co.za)
Out-of-bailiwick: 4 (za-ns.anycast.pch.net, za1.dnsnode.net, za-ns.anycast.pch.net...)
Analysis
IP Addresses
gets.co.za resolves to just one IP address, 102.130.122.156.
Two other host names, along with rooibank.co.za, fftc.co.za and icount.co.za, also share IP numbers with gets.co.za.
Name Servers
The NS records for gets.co.za point to four name servers: ns1.speedy-dns.com, ns2.speedy-dns.com, ns1.host-ww.net and ns2.host-ww.net.
There is at least partial name server overlap between gets.co.za and other domains — aldgatesolutions.com, capewed.co.za, selectedsupplies.com and two more among them.
The name servers ns1.ampledns.com, ns2.ampledns.com, ns3.host-ww.net and two others are commonly seen in use alongside these name servers.
Of the four host names ns1.speedy-dns.com, ns2.speedy-dns.com, ns1.host-ww.net and ns2.host-ww.net, each resolves to a single IP address: ns1.speedy-dns.com to 169.239.180.4, ns2.speedy-dns.com to 195.110.43.170, ns1.host-ww.net to 169.239.180.4 and ns2.host-ww.net to 195.110.43.170.
Both ns1.speedy-dns.com and ns1.host-ww.net resolve to 169.239.180.4 IP addresses each.
Both ns2.speedy-dns.com and ns2.host-ww.net resolve to 195.110.43.170 IP addresses each.
Mail Servers
Five mail servers handle gets.co.za: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between gets.co.za and other domains, including trendamental.com, ns500758.ns500758.ns500759.ns500759.ns500736.ns500735.ns500736.ns500698.ns500698.ns500735.ns500576.ns500576.ns500619.ns500686.ns500619.ns500619.trackreceptor.com, ns500731.ns500671.ns500754.ns500731.ns500742.ns500704.ns500731.ns500671.ns500671.ns500688.ns500671.ns500666.ns500291.ns500291.ns500291.ns500291.ns500131.lustychickser.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c21::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.