`go-schedule.com`

DNSSEC	⚠️ Not signed
A	16.62.97.248^{🇨🇭 Amazon16.62.0.0/15 EC2 ZRH Prefix}
		PTR	`ec2-16-62-97-248.eu-central-2.compute.amazonaws.com`
NS	`ns25.domaincontrol.com` ⭐
		A	2603:5:2161::d^{🇺🇸 GODADDY-DNS2603:5:2160::/44}
			PTR	`ns25.domaincontrol.com`
		A	97.74.102.13^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns25.domaincontrol.com`
NS	`ns26.domaincontrol.com`
		A	2603:5:2261::d^{🇺🇸 GODADDY-DNS2603:5:2260::/44}
			PTR	`ns26.domaincontrol.com`
		A	173.201.70.13^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns26.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4023:c03::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`dy-in-f26.1e100.net`
		A	74.125.137.26^{🇺🇸 Google74.125.137.0/24}
			PTR	`dy-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:2801::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`lcausi-in-f26.1e100.net`
		A	192.178.128.27^{🇺🇸 Google192.178.128.0/24}
			PTR	`lcausi-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c00::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`ws-in-f26.1e100.net`
			PTR	`ws-in-x1a.1e100.net`
		A	173.194.76.26^{🇺🇸 Google173.194.76.0/24}
			PTR	`ws-in-f26.1e100.net`
TXT	`v=spf1 include:_spf.google.com -all`
TXT	`google-site-verification=VL-SSHYBwZynL5IUoEVy3MpQZ9vmYqMEnjwi21bLLz0`
SOA	`ns25.domaincontrol.com`dns@jomax.net 2024-03-02 #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=1778764056

Same first word

go-schedule.com

DNS History

25 records (8 active, 17 former)

○NSns01.hostfactory.ch2020-02-02 → 2020-02-02 · 4 obs

○ 2017-03-22 20:24:04
● 2020-02-02 13:12:56
○ 2026-02-24 21:10:06
○ 2026-05-14 13:33:58

○NSns02.hostfactory.ch2020-02-02 → 2020-02-02 · 4 obs

○ 2017-03-22 20:24:04
● 2020-02-02 13:12:56
○ 2026-02-24 21:10:06
○ 2026-05-14 13:33:58

○NSns1.digitalocean.com2015-07-25 → 2015-07-25 · 3 obs

● 2015-07-25 22:57:12
○ 2015-12-06 19:29:46
○ 2026-05-14 13:33:58

○NSns17.domaincontrol.com2016-07-09 → 2017-03-22 · 5 obs

○ 2016-03-17 01:30:58
● 2016-07-09 11:09:46
● 2017-03-22 20:24:04
○ 2020-02-02 13:12:56
○ 2026-05-14 13:33:58

○NSns18.domaincontrol.com2016-07-09 → 2017-03-22 · 5 obs

○ 2016-03-17 01:30:58
● 2016-07-09 11:09:46
● 2017-03-22 20:24:04
○ 2020-02-02 13:12:56
○ 2026-05-14 13:33:58

○NSns2.digitalocean.com2015-07-25 → 2015-07-25 · 3 obs

● 2015-07-25 22:57:12
○ 2015-12-06 19:29:46
○ 2026-05-14 13:33:58

●NSns25.domaincontrol.com2026-02-24 → 2026-05-14 · 3 obs

○ 2020-02-02 13:12:56
● 2026-02-24 21:10:06
● 2026-05-14 13:33:58

●NSns26.domaincontrol.com2026-02-24 → 2026-05-14 · 3 obs

○ 2020-02-02 13:12:56
● 2026-02-24 21:10:06
● 2026-05-14 13:33:58

○NSns3.digitalocean.com2015-07-25 → 2015-07-25 · 3 obs

● 2015-07-25 22:57:12
○ 2015-12-06 19:29:46
○ 2026-05-14 13:33:58

○NSns53.domaincontrol.com2016-03-17 → 2016-03-17 · 4 obs

○ 2015-12-06 19:29:46
● 2016-03-17 01:30:58
○ 2016-07-09 11:09:46
○ 2026-05-14 13:33:58

○NSns54.domaincontrol.com2016-03-17 → 2016-03-17 · 4 obs

○ 2015-12-06 19:29:46
● 2016-03-17 01:30:58
○ 2016-07-09 11:09:46
○ 2026-05-14 13:33:58

●MXalt1.aspmx.l.google.com2026-02-24 → 2026-05-14 · 3 obs

○ 2020-02-02 13:12:56
● 2026-02-24 21:10:06
● 2026-05-14 13:33:58

●MXalt2.aspmx.l.google.com2026-02-24 → 2026-05-14 · 3 obs

○ 2020-02-02 13:12:56
● 2026-02-24 21:10:06
● 2026-05-14 13:33:58

●MXalt3.aspmx.l.google.com2026-02-24 → 2026-05-14 · 3 obs

○ 2020-02-02 13:12:56
● 2026-02-24 21:10:06
● 2026-05-14 13:33:58

●MXalt4.aspmx.l.google.com2026-02-24 → 2026-05-14 · 3 obs

○ 2020-02-02 13:12:56
● 2026-02-24 21:10:06
● 2026-05-14 13:33:58

●MXaspmx.l.google.com2026-02-24 → 2026-05-14 · 3 obs

○ 2020-02-02 13:12:56
● 2026-02-24 21:10:06
● 2026-05-14 13:33:58

○MXmail.go-schedule.com2016-03-17 → 2017-03-22 · 4 obs

● 2016-03-17 01:30:58
● 2017-03-22 20:24:04
○ 2020-02-02 13:12:56
○ 2026-05-14 13:33:58

○MXmx1.hostfactory.ch2020-02-02 → 2020-02-02 · 4 obs

○ 2017-03-22 20:24:04
● 2020-02-02 13:12:56
○ 2026-02-24 21:10:06
○ 2026-05-14 13:33:58

○MXmx2.hostfactory.swiss2020-02-02 → 2020-02-02 · 4 obs

○ 2017-03-22 20:24:04
● 2020-02-02 13:12:56
○ 2026-02-24 21:10:06
○ 2026-05-14 13:33:58

○MXmx3.hostfactory.ch2020-02-02 → 2020-02-02 · 4 obs

○ 2017-03-22 20:24:04
● 2020-02-02 13:12:56
○ 2026-02-24 21:10:06
○ 2026-05-14 13:33:58

○MXmx4.hostfactory.swiss2020-02-02 → 2020-02-02 · 4 obs

○ 2017-03-22 20:24:04
● 2020-02-02 13:12:56
○ 2026-02-24 21:10:06
○ 2026-05-14 13:33:58

●A16.62.97.2482026-02-24 → 2026-05-14 · 3 obs

○ 2020-02-02 13:12:56
● 2026-02-24 21:10:06
● 2026-05-14 13:33:58

○A160.153.16.442016-03-17 → 2017-03-22 · 5 obs

○ 2015-12-06 19:29:46
● 2016-03-17 01:30:58
● 2017-03-22 20:24:04
○ 2020-02-02 13:12:56
○ 2026-05-14 13:33:58

○A185.117.168.2142020-02-02 → 2020-02-02 · 4 obs

○ 2017-03-22 20:24:04
● 2020-02-02 13:12:56
○ 2026-02-24 21:10:06
○ 2026-05-14 13:33:58

○A198.199.117.1252015-07-25 → 2015-07-25 · 3 obs

● 2015-07-25 22:57:12
○ 2015-12-06 19:29:46
○ 2026-05-14 13:33:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
go-schedule.com	ns25.domaincontrol.com, ns26.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.102.13

NS records: ns25.domaincontrol.com, ns26.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for go-schedule.com (unsigned zone)

⏱️ Timing

Total: 1468ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`16.62.97.248`
NS	2	`ns25.domaincontrol.com, ns26.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	2	`v=spf1 include:_spf.google.com -all, google-site-verification=VL-SSHYBwZynL5I`
SOA	1	`ns25.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns25.domaincontrol.com, ns25.domaincontrol.com, ns26.domaincontrol.com...)

Analysis

IP Addresses

go-schedule.com points to a single IP number: 16.62.97.248.

Other host names, for instance ec2-16-62-97-248.eu-central-2.compute.amazonaws.com, share IP numbers with go-schedule.com.

Name Servers

go-schedule.com is delegated to two name servers: ns25.domaincontrol.com and ns26.domaincontrol.com.

go-schedule.com shares the same name server setup as other domains, for example astandards.com, pemostudio.com, whataperfume.com, callercomplaint.com and carrpull.com.

Host names with two IP numbers:

ns25.domaincontrol.com points to 2603:5:2161::d and 97.74.102.13

ns26.domaincontrol.com points to 2603:5:2261::d and 173.201.70.13

Mail Servers

go-schedule.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.

go-schedule.com shares mail servers with other domains at least partially, including miladj.com, all3dp.com, alohatable.com, drivewaydoctor.com and joinvento.com.