`dbstechnology.joburg`

DNSSEC	⚠️ Not signed
A	41.203.16.85^{🇿🇦 xneelo41.203.16.0/20 -JHB-BLK}
		PTR	`dedi568.jnb3.host-h.net`
NS	`ns1.host-h.net` ⭐
		A	129.232.248.30^{🇿🇦 xneelo129.232.248.0/24 AnyCast DNS}
			PTR	`ns1.host-h.net`
NS	`ns1.dns-h.com`
		A	129.232.248.31^{🇿🇦 xneelo129.232.248.0/24 AnyCast DNS}
			PTR	`ns1.dns-h.com`
NS	`ns2.dns-h.com`
		A	129.232.248.41^{🇿🇦 xneelo129.232.248.0/24 AnyCast DNS}
			PTR	`ns2.dns-h.com`
NS	`ns2.host-h.net`
		A	129.232.248.40^{🇿🇦 xneelo129.232.248.0/24 AnyCast DNS}
			PTR	`ns2.host-h.net`
MX	`za-smtp-inbound-1.mimecast.co.za` ⭐
		A	41.74.193.201^{🇿🇦 MimecastSA41.74.193.0/24 Mimecast SA}
			PTR	`za-smtp-inbound-1.mimecast.co.za`
			PTR	`za-smtp-inbound-2.mimecast.co.za`
		A	41.74.193.210^{🇿🇦 MimecastSA41.74.193.0/24 Mimecast SA}
			PTR	`za-smtp-inbound-1.mimecast.co.za`
			PTR	`za-smtp-inbound-2.mimecast.co.za`
		A	41.74.197.201^{🇿🇦 MimecastSA41.74.196.0/22 Mimecast SA}
			PTR	`za-smtp-inbound-1.mimecast.co.za`
			PTR	`za-smtp-inbound-2.mimecast.co.za`
		A	41.74.197.210^{🇿🇦 MimecastSA41.74.196.0/22 Mimecast SA}
			PTR	`za-smtp-inbound-1.mimecast.co.za`
			PTR	`za-smtp-inbound-2.mimecast.co.za`
MX	`za-smtp-inbound-2.mimecast.co.za` ⭐
		A	41.74.193.201^{🇿🇦 MimecastSA41.74.193.0/24 Mimecast SA}
			PTR	`za-smtp-inbound-1.mimecast.co.za`
			PTR	`za-smtp-inbound-2.mimecast.co.za`
		A	41.74.193.210^{🇿🇦 MimecastSA41.74.193.0/24 Mimecast SA}
			PTR	`za-smtp-inbound-1.mimecast.co.za`
			PTR	`za-smtp-inbound-2.mimecast.co.za`
		A	41.74.197.201^{🇿🇦 MimecastSA41.74.196.0/22 Mimecast SA}
			PTR	`za-smtp-inbound-1.mimecast.co.za`
			PTR	`za-smtp-inbound-2.mimecast.co.za`
		A	41.74.197.210^{🇿🇦 MimecastSA41.74.196.0/22 Mimecast SA}
			PTR	`za-smtp-inbound-1.mimecast.co.za`
			PTR	`za-smtp-inbound-2.mimecast.co.za`
TXT	`v=spf1 include:_netblocks.mimecast.com ~all.`
SOA	`ns1.host-h.net`postmaster@your-server.co.za 2021-10-02 #0

`joburg`

	DNSSEC	🔒 Signed (DS record present)
	NS	`zone-ds.registry.net.za` ⭐
	NS	`coza1.dnsnode.net`
	NS	`ns2.dns.net.za`
	NS	`ns4.dns.net.za`
	SOA	`zone-ds.registry.net.za`support@registry.net.za 2025-07-04 #18

Same first word

dbstechnology.capetown

dbstechnology.joburg

Similar names

bdstechnology.co.uk

DNS History

9 records (7 active, 2 former)

●NSns1.dns-h.com2016-12-13 → 2026-04-24 · 2 obs

● 2016-12-13 03:28:24
● 2026-04-24 14:58:00

●NSns1.host-h.net2016-12-13 → 2026-04-24 · 2 obs

● 2016-12-13 03:28:24
● 2026-04-24 14:58:00

●NSns2.dns-h.com2016-12-13 → 2026-04-24 · 2 obs

● 2016-12-13 03:28:24
● 2026-04-24 14:58:00

●NSns2.host-h.net2016-12-13 → 2026-04-24 · 2 obs

● 2016-12-13 03:28:24
● 2026-04-24 14:58:00

○MXdbstechnology-joburg.mail.protection.outlook.com2016-12-13 → 2017-07-06 · 4 obs

● 2016-12-13 03:28:24
● 2017-07-06 15:11:10
○ 2026-03-05 13:54:46
○ 2026-04-24 14:58:00

●MXza-smtp-inbound-1.mimecast.co.za2026-03-05 → 2026-04-24 · 3 obs

○ 2017-07-06 15:11:10
● 2026-03-05 13:54:46
● 2026-04-24 14:58:00

●MXza-smtp-inbound-2.mimecast.co.za2026-03-05 → 2026-04-24 · 3 obs

○ 2017-07-06 15:11:10
● 2026-03-05 13:54:46
● 2026-04-24 14:58:00

○A196.22.142.412016-12-13 → 2017-07-06 · 4 obs

● 2016-12-13 03:28:24
● 2017-07-06 15:11:10
○ 2026-03-05 13:54:46
○ 2026-04-24 14:58:00

●A41.203.16.852026-03-05 → 2026-04-24 · 3 obs

○ 2017-07-06 15:11:10
● 2026-03-05 13:54:46
● 2026-04-24 14:58:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
joburg	ns2.dns.net.za, coza1.dnsnode.net, ns4.dns.net.za	6 records
dbstechnology.joburg	ns1.host-h.net, ns2.host-h.net, ns1.dns-h.com, ns2.dns-h.com	-

✅ Authoritative Response

Server:129.232.248.30

NS records: ns1.host-h.net, ns2.host-h.net, ns1.dns-h.com, ns2.dns-h.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dbstechnology.joburg (unsigned zone)

⏱️ Timing

Total: 3896ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`41.203.16.85`
NS	4	`ns2.host-h.net, ns1.host-h.net...`
MX	2	`za-smtp-inbound-2.mimecast.co.za (pri: 1, za-smtp-inbound-1.mimecast.co.za (pri: 1`
TXT	1	`v=spf1 include:_netblocks.mimecast.com ~`
SOA	1	`ns1.host-h.net postmaster.your-server.co`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns2.dns.net.za, ns2.dns.net.za, coza1.dnsnode.net...)

Analysis

IP Addresses

dbstechnology.joburg points to a single IP address: 41.203.16.85.

Other host names such as tct.co.za, madhlopa.co.za, inscape.co.za, chrisvuba.com and dbstech.co.za share IPs with dbstechnology.joburg.

Name Servers

dbstechnology.joburg is delegated to four name servers: ns1.dns-h.com, ns2.dns-h.com, ns1.host-h.net and ns2.host-h.net.

dbstechnology.joburg at least partially shares name servers with other domains, for example michalsonsattorneys.com, ltta.co.za, getdriven.co.za, fusia.co.za and mieliemeisie.com.

These name servers are often used with ns1a.your-server.co.za, ns1-06.azure-dns.com, ns4-06.azure-dns.info, ns2-06.azure-dns.net and ns3-06.azure-dns.org.

Host names with one IP number:

ns1.dns-h.com points to: 129.232.248.31

ns2.dns-h.com points to: 129.232.248.41

ns1.host-h.net points to: 129.232.248.30

ns2.host-h.net points to: 129.232.248.40

Mail Servers

Two mail servers handle dbstechnology.joburg: za-smtp-inbound-1.mimecast.co.za and za-smtp-inbound-2.mimecast.co.za.

dbstechnology.joburg shares the same mail server setup as other domains, including cbi.co.za, onelogix.com, affirm.co.za, convergedgroup.net and firstnet.co.za.

dbstechnology.joburg shares at least partially some mail servers with other domains, for instance fema.co.za, satib.co.za, samancorcr.com, busamed.co.za and unitransafrica.com.