`sinansys.com`

DNSSEC	⚠️ Not signed
A	3.33.251.168^{🇺🇸 Amazon3.33.240.0/20}
		PTR	`aec037177372cc6cd.awsglobalaccelerator.com`
A	15.197.225.128^{🇺🇸 Amazon15.197.224.0/20}
NS	`ns37.domaincontrol.com` ⭐
		A	2603:5:21c1::13^{🇺🇸 GODADDY-DNS2603:5:21c0::/44}
			PTR	`ns37.domaincontrol.com`
		A	97.74.108.19^{🇺🇸 GODADDY-DNS97.74.108.0/23}
			PTR	`ns37.domaincontrol.com`
NS	`ns38.domaincontrol.com`
		A	2603:5:22c1::13^{🇺🇸 GODADDY-DNS2603:5:22c0::/44}
			PTR	`ns38.domaincontrol.com`
		A	173.201.76.19^{🇺🇸 GODADDY-DNS173.201.76.0/23}
			PTR	`ns38.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4023:c0b::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`dd-in-f26.1e100.net`
		A	142.251.2.27^{🇺🇸 Google142.251.2.0/24}
			PTR	`ip-142-251-2-27.defastlink.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4025:402::1a^{🇳🇱 Google2a00:1450:4025::/48}
			PTR	`rb-in-f26.1e100.net`
		A	142.250.102.26^{🇺🇸 Google142.250.102.0/24}
			PTR	`ip-142-250-102-26.defastlink.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:1015::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yudfwta-in-f27.1e100.net`
		A	172.253.135.26^{🇺🇸 Google172.253.135.0/24}
			PTR	`yudfwta-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2607:f8b0:4023:3003::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yulnkjt-in-f27.1e100.net`
		A	172.253.145.26^{🇺🇸 Google172.253.145.0/24}
			PTR	`yulnkjt-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2607:f8b0:4003:c4a::1b^{🇺🇸 Google2607:f8b0:4003::/48}
			PTR	`yutulth-in-f27.1e100.net`
		A	142.251.96.27^{🇺🇸 Google142.250.0.0/15}
			PTR	`yutulth-in-f27.1e100.net`
TXT	`d5678814-5a9d-4510-bc5a-27db79f91642`
TXT	`_webflow one-time-verification=d5678814-5a9d-4510-bc5a-27db79f91642`
TXT	`TXT _webflow one-time-verification=d5678814-5a9d-4510-bc5a-27db79f91642`
TXT	`v=spf1 include:dc-aa8e722993._spfm.sinansys.com ~all`
TXT	`google-site-verification=TWPW9S0zfuJW4tPowfV-_z7w1YnuUWizOl2lrjL1UPw`
SOA	`ns37.domaincontrol.com`dns@jomax.net 2026-03-19 #0

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

Same first word

sinansys.com

DNS History

14 records (9 active, 5 former)

○NSns.opengogo.com2015-07-13 → 2017-12-21 · 3 obs

● 2015-07-13 10:50:14
● 2017-12-21 22:40:04
○ 2026-03-28 10:16:20

○NSns.openhaja.com2015-07-13 → 2017-12-21 · 3 obs

● 2015-07-13 10:50:14
● 2017-12-21 22:40:04
○ 2026-03-28 10:16:20

●NSns37.domaincontrol.com2026-03-28 → 2026-03-28 · 2 obs

○ 2017-12-21 22:40:04
● 2026-03-28 10:16:20

●NSns38.domaincontrol.com2026-03-28 → 2026-03-28 · 2 obs

○ 2017-12-21 22:40:04
● 2026-03-28 10:16:20

○NSsinansys.com2015-07-13 → 2017-12-21 · 3 obs

● 2015-07-13 10:50:14
● 2017-12-21 22:40:04
○ 2026-03-28 10:16:20

●MXalt1.aspmx.l.google.com2026-03-28 → 2026-03-28 · 2 obs

○ 2017-12-21 22:40:04
● 2026-03-28 10:16:20

●MXalt2.aspmx.l.google.com2026-03-28 → 2026-03-28 · 2 obs

○ 2017-12-21 22:40:04
● 2026-03-28 10:16:20

●MXalt3.aspmx.l.google.com2026-03-28 → 2026-03-28 · 2 obs

○ 2017-12-21 22:40:04
● 2026-03-28 10:16:20

●MXalt4.aspmx.l.google.com2026-03-28 → 2026-03-28 · 2 obs

○ 2017-12-21 22:40:04
● 2026-03-28 10:16:20

●MXaspmx.l.google.com2026-03-28 → 2026-03-28 · 2 obs

○ 2017-12-21 22:40:04
● 2026-03-28 10:16:20

○MXmail.sinansys.com2015-07-13 → 2017-12-21 · 3 obs

● 2015-07-13 10:50:14
● 2017-12-21 22:40:04
○ 2026-03-28 10:16:20

○A121.78.91.142015-07-13 → 2017-12-21 · 3 obs

● 2015-07-13 10:50:14
● 2017-12-21 22:40:04
○ 2026-03-28 10:16:20

●A15.197.225.1282026-03-28 → 2026-03-28 · 2 obs

○ 2017-12-21 22:40:04
● 2026-03-28 10:16:20

●A3.33.251.1682026-03-28 → 2026-03-28 · 2 obs

○ 2017-12-21 22:40:04
● 2026-03-28 10:16:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
sinansys.com	ns37.domaincontrol.com, ns38.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.76.19

NS records: ns37.domaincontrol.com, ns38.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sinansys.com (unsigned zone)

⏱️ Timing

Total: 76ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`15.197.225.128, 3.33.251.168`
NS	2	`ns37.domaincontrol.com, ns38.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	5	`d5678814-5a9d-4510-bc5a-27db79f91642, _webflow one-time-verification=d5678814-...`
SOA	1	`ns37.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns37.domaincontrol.com, ns37.domaincontrol.com, ns38.domaincontrol.com...)

Analysis

IP Addresses

sinansys.com points to two IP numbers: 3.33.251.168 and 15.197.225.128.

Other host names such as sans-serif-fonts.com, galionveterinaryhospital.com, aroundme.co.in, 008579.com and csautos.ca share IPs with sinansys.com.

Name Servers

Two name servers ns37.domaincontrol.com and ns38.domaincontrol.com handle the delegation for sinansys.com.

sinansys.com shares the same name server setup as other domains, for example vireevangiles.com, ivorysummit.com, ctrlbee.com, withyoubirthing.com and 0402288.com.

Host names with two IP numbers:

ns37.domaincontrol.com points to 2603:5:21c1::13 and 97.74.108.19.

ns38.domaincontrol.com points to 2603:5:22c1::13 and 173.201.76.19.

Mail Servers

sinansys.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.

sinansys.com shares at least partially some mail servers with other domains, for instance corpa.io, verrus.de, scalora.net, rhqdigital.co.uk and gimang.com.