trinitysys.net - dns.ninja

`trinitysys.net`

DNSSEC	⚠️ Not signed
A	208.109.77.225^{🇺🇸 AS398101208.109.64.0/20}
NS	`ns41.domaincontrol.com` ⭐
		A	2603:5:2142::15^{🇺🇸 GODADDY-DNS2603:5:2140::/44}
			PTR	`ns41.domaincontrol.com`
		A	97.74.100.21^{🇺🇸 GODADDY-DNS97.74.100.0/23}
NS	`ns42.domaincontrol.com`
		A	2603:5:2242::15^{🇺🇸 GODADDY-DNS2603:5:2240::/44}
			PTR	`ns42.domaincontrol.com`
		A	173.201.68.21^{🇺🇸 GODADDY-DNS173.201.68.0/23}
MX	`trinitysys-net.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr03cu01703.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch5pr02cu00200.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch0pr04cu00603.inbound.protection.outlook.com`
		A	2a01:111:f403:f902::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mn2pr02cu00202.inbound.protection.outlook.com`
		A	52.101.9.2^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
		A	52.101.9.5^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mn2pr04cu00205.inbound.protection.outlook.com`
		A	52.101.9.11^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr04cu00103.inbound.protection.outlook.com`
		A	52.101.11.15^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
TXT	`NETORGFT3746331.onmicrosoft.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns41.domaincontrol.com`dns@jomax.net 2026-05-29 #0

	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.net`nstld@verisign-grs.com serial=1782839336

trinitysys.net

4 records (4 active, 0 former)

●NSns41.domaincontrol.com2026-02-23 → 2026-06-30 · 2 obs

● 2026-02-23 12:36:20
● 2026-06-30 17:30:32

●NSns42.domaincontrol.com2026-02-23 → 2026-06-30 · 2 obs

● 2026-02-23 12:36:20
● 2026-06-30 17:30:32

●MXtrinitysys-net.mail.protection.outlook.com2026-02-23 → 2026-06-30 · 2 obs

● 2026-02-23 12:36:20
● 2026-06-30 17:30:32

●A208.109.77.2252026-02-23 → 2026-06-30 · 2 obs

● 2026-02-23 12:36:20
● 2026-06-30 17:30:32

Zone	Nameservers	Glue
net	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
trinitysys.net	ns41.domaincontrol.com, ns42.domaincontrol.com	-

Server:97.74.100.21

NS records: ns41.domaincontrol.com, ns42.domaincontrol.com

⚠️ Insecure (no DNSSEC)

No DS record for trinitysys.net (unsigned zone)

Total: 285ms | Queries: -

Type	Count	Sample Data
A	1	`208.109.77.225`
NS	2	`ns41.domaincontrol.com, ns42.domaincontrol.com`
MX	1	`trinitysys-net.mail.protection.outlook.c`
TXT	2	`NETORGFT3746331.onmicrosoft.com, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns41.domaincontrol.com dns.jomax.net`

trinitysys.net resolves to one IP address: 208.109.77.225.

monterrey.com, tinaweiss.com, thelanguagepros.com and two other host names share IP numbers with trinitysys.net.

The NS records for trinitysys.net delegate to ns41.domaincontrol.com and ns42.domaincontrol.com.

trinitysys.net uses the same name servers as several other domains — among them ritenow.us, dermx.com, myindexcards.com and two more.

trinitysys.net and other domains like ploppy.co.uk share at least a portion of their name servers.

Mail for trinitysys.net is handled by a single mail server, trinitysys-net.mail.protection.outlook.com.