getsynapse.com - dns.ninja

`getsynapse.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	`ns35.domaincontrol.com` ⭐
		A	2603:5:21b1::12^{🇺🇸 GODADDY-DNS2603:5:21b0::/44}
			PTR	`ns35.domaincontrol.com`
		A	97.74.107.18^{🇺🇸 GODADDY-DNS97.74.106.0/23}
			PTR	`ns35.domaincontrol.com`
NS	`ns36.domaincontrol.com`
		A	2603:5:22b1::12^{🇺🇸 GODADDY-DNS2603:5:22b0::/44}
			PTR	`ns36.domaincontrol.com`
		A	173.201.75.18^{🇺🇸 GODADDY-DNS173.201.74.0/23}
			PTR	`ns36.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c19::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bk-in-f26.1e100.net`
		A	142.251.16.27^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽²⁰⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽³⁰⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`aspmx2.googlemail.com`⁽⁴⁰⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`aspmx3.googlemail.com`⁽⁵⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
TXT	`ve0g7e8t69lr3jfd2ss39rp26o`
TXT	`_globalsign-domain-verification=IG4UdrI9gc_SVSE132aTagdWhxkvONdbIBhHhhcMlP`
TXT	`EyoWv5tF83VpeFOrGy9NDiQa3R3PgS6zx+qFB+mRwyQ=`
TXT	`atlassian-domain-verification=IYE35Hmqq2IAPv895i5EqQ0EZqX0eESA9s2xnJ1e3+zRP+a...`
TXT	`v=spf1 include:amazonses.com include:_spf.google.com include:2229219.spf05.hu...`
TXT	`google-site-verification=fqRVWWbyuiqcMIq7y2fmWrZQzxovnVLg9Rp71ez2wQM`
TXT	`519A57A796`
TXT	`MS=ms65787615`
TXT	`facebook-domain-verification=wmsvce5vkjbd1j6iu6e2nv1xougnls`
SOA	`ns35.domaincontrol.com`dns@jomax.net 2026-06-05 #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=1786360844

Subdomains

filemanagerdev.getsynapse.com

trainingbackprod.getsynapse.com

info.getsynapse.com

Same first word

getsynapse.io

getsynapse.com

DNS History

24 records (9 active, 15 former)

○NSdns1.registrar-servers.com2016-01-21 → 2016-09-21 · 5 obs

● 2016-01-21 04:30:56
○ 2016-04-17 13:37:08
● 2016-09-21 16:56:44
○ 2017-04-20 02:29:36
○ 2026-08-10 11:36:32

○NSdns1.registrar-servers.com,2016-04-17 → 2016-09-21 · 5 obs

○ 2016-01-21 04:30:56
● 2016-04-17 13:37:08
● 2016-09-21 16:56:44
○ 2017-04-20 02:29:36
○ 2026-08-10 11:36:32

○NSdns2.registrar-servers.com2016-01-21 → 2016-09-21 · 4 obs

● 2016-01-21 04:30:56
● 2016-09-21 16:56:44
○ 2017-04-20 02:29:36
○ 2026-08-10 11:36:32

○NSdns3.registrar-servers.com2016-01-21 → 2016-09-21 · 4 obs

● 2016-01-21 04:30:56
● 2016-09-21 16:56:44
○ 2017-04-20 02:29:36
○ 2026-08-10 11:36:32

○NSdns4.registrar-servers.com2016-01-21 → 2016-09-21 · 4 obs

● 2016-01-21 04:30:56
● 2016-09-21 16:56:44
○ 2017-04-20 02:29:36
○ 2026-08-10 11:36:32

○NSdns5.registrar-servers.com2016-01-21 → 2016-09-21 · 4 obs

● 2016-01-21 04:30:56
● 2016-09-21 16:56:44
○ 2017-04-20 02:29:36
○ 2026-08-10 11:36:32

●NSns35.domaincontrol.com2017-04-20 → 2026-08-10 · 3 obs

○ 2016-09-21 16:56:44
● 2017-04-20 02:29:36
● 2026-08-10 11:36:32

●NSns36.domaincontrol.com2017-04-20 → 2026-08-10 · 3 obs

○ 2016-09-21 16:56:44
● 2017-04-20 02:29:36
● 2026-08-10 11:36:32

●MXalt1.aspmx.l.google.com2017-04-20 → 2026-08-10 · 3 obs

○ 2016-09-21 16:56:44
● 2017-04-20 02:29:36
● 2026-08-10 11:36:32

●MXalt2.aspmx.l.google.com2017-04-20 → 2026-08-10 · 3 obs

○ 2016-09-21 16:56:44
● 2017-04-20 02:29:36
● 2026-08-10 11:36:32

●MXaspmx.l.google.com2017-04-20 → 2026-08-10 · 3 obs

○ 2016-09-21 16:56:44
● 2017-04-20 02:29:36
● 2026-08-10 11:36:32

●MXaspmx2.googlemail.com2017-04-20 → 2026-08-10 · 3 obs

○ 2016-09-21 16:56:44
● 2017-04-20 02:29:36
● 2026-08-10 11:36:32

●MXaspmx3.googlemail.com2017-04-20 → 2026-08-10 · 3 obs

○ 2016-09-21 16:56:44
● 2017-04-20 02:29:36
● 2026-08-10 11:36:32

○MXeforward1.registrar-servers.com2016-01-21 → 2016-09-21 · 4 obs

● 2016-01-21 04:30:56
● 2016-09-21 16:56:44
○ 2017-04-20 02:29:36
○ 2026-08-10 11:36:32

○MXeforward2.registrar-servers.com2016-01-21 → 2016-09-21 · 4 obs

● 2016-01-21 04:30:56
● 2016-09-21 16:56:44
○ 2017-04-20 02:29:36
○ 2026-08-10 11:36:32

○MXeforward3.registrar-servers.com2016-01-21 → 2016-09-21 · 4 obs

● 2016-01-21 04:30:56
● 2016-09-21 16:56:44
○ 2017-04-20 02:29:36
○ 2026-08-10 11:36:32

○MXeforward4.registrar-servers.com2016-01-21 → 2016-09-21 · 4 obs

● 2016-01-21 04:30:56
● 2016-09-21 16:56:44
○ 2017-04-20 02:29:36
○ 2026-08-10 11:36:32

○MXeforward5.registrar-servers.com2016-01-21 → 2016-09-21 · 4 obs

● 2016-01-21 04:30:56
● 2016-09-21 16:56:44
○ 2017-04-20 02:29:36
○ 2026-08-10 11:36:32

●A15.197.225.1282026-02-16 → 2026-08-10 · 3 obs

○ 2017-04-20 02:29:36
● 2026-02-16 04:54:02
● 2026-08-10 11:36:32

○A162.255.119.2512016-01-21 → 2016-01-21 · 4 obs

○ 2015-10-25 21:48:08
● 2016-01-21 04:30:56
○ 2016-04-17 13:37:08
○ 2026-08-10 11:36:32

○A166.62.108.2302017-04-20 → 2017-04-20 · 4 obs

○ 2016-09-21 16:56:44
● 2017-04-20 02:29:36
○ 2026-02-16 04:54:02
○ 2026-08-10 11:36:32

○A192.64.119.702016-04-17 → 2016-09-21 · 5 obs

○ 2016-01-21 04:30:56
● 2016-04-17 13:37:08
● 2016-09-21 16:56:44
○ 2017-04-20 02:29:36
○ 2026-08-10 11:36:32

●A3.33.251.1682026-02-16 → 2026-08-10 · 3 obs

○ 2017-04-20 02:29:36
● 2026-02-16 04:54:02
● 2026-08-10 11:36:32

○A72.47.223.1102008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 22:48:16
○ 2015-10-25 21:48:08
○ 2026-08-10 11:36:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
getsynapse.com	ns35.domaincontrol.com, ns36.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.75.18

NS records: ns35.domaincontrol.com, ns36.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for getsynapse.com (unsigned zone)

⏱️ Timing

Total: 171ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`15.197.225.128, 3.33.251.168`
NS	2	`ns35.domaincontrol.com, ns36.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 20)...`
TXT	9	`ve0g7e8t69lr3jfd2ss39rp26o, _globalsign-domain-verification=IG4UdrI9...`
SOA	1	`ns35.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns35.domaincontrol.com, ns35.domaincontrol.com, ns36.domaincontrol.com...)

Analysis

Hierarchy

getsynapse.com is a parent domain, with filemanagerdev.getsynapse.com, trainingbackprod.getsynapse.com and info.getsynapse.com beneath it.

IP Addresses

getsynapse.com resolves to the IP addresses 3.33.251.168 and 15.197.225.128

montecito-homefinder.com, summerhaysstrings.com, 4seasonstravel.net plus two other host names have IP numbers in common with getsynapse.com.

Name Servers

getsynapse.com uses two name servers for its delegation: ns35.domaincontrol.com and ns36.domaincontrol.com.

The name server configuration of getsynapse.com is shared with other domains, for instance suutam.net, pinzo.school, healthyhomeshub.uk and two others.

The two host names ns35.domaincontrol.com and ns36.domaincontrol.com each have a pair of IP addresses: ns35.domaincontrol.com has 97.74.107.18 and 2603:5:21b1::12, and ns36.domaincontrol.com has 173.201.75.18 and 2603:5:22b1::12.

Mail Servers

getsynapse.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

At least some of the mail servers used by getsynapse.com are shared with other domains: valla.nu, accord.com.tw, deviceparadigm.com and two others among them.

These mail servers are often deployed together with alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx2.googlemail.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1b.

aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.

aspmx.l.google.com directs traffic to 142.251.16.27 and 2607:f8b0:4004:c19::1a.

alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.

alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.

Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.27 IP addresses each.