setprotocol.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`setprotocol.com`

DNSSEC	⚠️ Not signed
NS	`dns1.registrar-servers.com` ⭐
		A	2610:a1:1024::200^{🇺🇸 MAINT-ID-120082610:a1:1024::/48 Neustar}
			PTR	`dns1.namecheaphosting.com`
			PTR	`dns1.registrar-servers.com`
		A	156.154.132.200^{🇺🇸 MAINT-ID-12008156.154.132.0/24 Neustar}
			PTR	`dns1.namecheaphosting.com`
			PTR	`dns1.registrar-servers.com`
NS	`dns2.registrar-servers.com`
		A	2610:a1:1025::200^{🇺🇸 MAINT-ID-120082610:a1:1025::/48 Neustar}
			PTR	`dns2.namecheaphosting.com`
			PTR	`dns2.registrar-servers.com`
		A	156.154.133.200^{🇺🇸 MAINT-ID-12008156.154.133.0/24 Neustar}
			PTR	`dns2.namecheaphosting.com`
			PTR	`dns2.registrar-servers.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c09::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bh-in-f27.1e100.net`
		A	142.251.163.26^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f26.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::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.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.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
SOA	`dns1.registrar-servers.com`hostmaster@registrar-servers.com serial=1729447375

`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=1790597804

Same first word

setprotocol.com

setprotocol.eu

Similar names

Previous names

Next names

DNS History

13 records (7 active, 6 former)

●NSdns1.registrar-servers.com2017-10-16 → 2026-09-28 · 2 obs

● 2017-10-16 03:16:22
● 2026-09-28 12:22:24

●NSdns2.registrar-servers.com2017-10-16 → 2026-09-28 · 2 obs

● 2017-10-16 03:16:22
● 2026-09-28 12:22:24

●MXalt1.aspmx.l.google.com2026-08-18 → 2026-09-28 · 3 obs

○ 2017-10-16 03:16:22
● 2026-08-18 12:56:10
● 2026-09-28 12:22:24

●MXalt2.aspmx.l.google.com2026-08-18 → 2026-09-28 · 3 obs

○ 2017-10-16 03:16:22
● 2026-08-18 12:56:10
● 2026-09-28 12:22:24

●MXaspmx.l.google.com2026-08-18 → 2026-09-28 · 3 obs

○ 2017-10-16 03:16:22
● 2026-08-18 12:56:10
● 2026-09-28 12:22:24

●MXaspmx2.googlemail.com2026-08-18 → 2026-09-28 · 3 obs

○ 2017-10-16 03:16:22
● 2026-08-18 12:56:10
● 2026-09-28 12:22:24

●MXaspmx3.googlemail.com2026-08-18 → 2026-09-28 · 3 obs

○ 2017-10-16 03:16:22
● 2026-08-18 12:56:10
● 2026-09-28 12:22:24

○MXeforward1.registrar-servers.com2017-10-16 → 2017-10-16 · 3 obs

● 2017-10-16 03:16:22
○ 2026-08-18 12:56:10
○ 2026-09-28 12:22:24

○MXeforward2.registrar-servers.com2017-10-16 → 2017-10-16 · 3 obs

● 2017-10-16 03:16:22
○ 2026-08-18 12:56:10
○ 2026-09-28 12:22:24

○MXeforward3.registrar-servers.com2017-10-16 → 2017-10-16 · 3 obs

● 2017-10-16 03:16:22
○ 2026-08-18 12:56:10
○ 2026-09-28 12:22:24

○MXeforward4.registrar-servers.com2017-10-16 → 2017-10-16 · 3 obs

● 2017-10-16 03:16:22
○ 2026-08-18 12:56:10
○ 2026-09-28 12:22:24

○MXeforward5.registrar-servers.com2017-10-16 → 2017-10-16 · 3 obs

● 2017-10-16 03:16:22
○ 2026-08-18 12:56:10
○ 2026-09-28 12:22:24

○A162.255.119.1892017-10-16 → 2017-10-16 · 3 obs

● 2017-10-16 03:16:22
○ 2026-08-18 12:56:10
○ 2026-09-28 12:22:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, f.gtld-servers.net, m.gtld-servers.net, j.gtld-servers.net...	-
setprotocol.com	dns1.registrar-servers.com, dns2.registrar-servers.com	4 records

✅ Authoritative Response

Server:156.154.133.200

NS records: dns1.registrar-servers.com, dns2.registrar-servers.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for setprotocol.com (unsigned zone)

⏱️ Timing

Total: 421ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`dns1.registrar-servers.com, dns2.registrar-servers.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
SOA	1	`dns1.registrar-servers.com hostmaster.re`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)

Analysis

Name Servers

setprotocol.com has two authoritative name servers — dns1.registrar-servers.com and dns2.registrar-servers.com.

setprotocol.com has the same name server delegation as a number of other domains, such as kernelsandkeys.org, johnmuirfitness.com, lovera.co and two more.

There is an overlap in name servers between setprotocol.com and other domains, for example empathylaboratory.org, ukeac.net and ryanremodelingli.com

It is common for these name servers to be used in conjunction with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.

Both dns1.registrar-servers.com and dns2.registrar-servers.com have two IP addresses each. dns1.registrar-servers.com resolves to 156.154.132.200 and 2610:a1:1024::200; dns2.registrar-servers.com resolves to 156.154.133.200 and 2610:a1:1025::200.

Mail Servers

Five mail servers handle setprotocol.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

setprotocol.com shares at least some of its mail servers with other domains — for example itsmguru.au, radiusemail.com, kwalede.com and two more.

It is common to find these mail servers paired with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 more.

Hosts with two IP numbers each:

aspmx2.googlemail.com resolves to 192.178.234.27 and 2800:3f0:4003:c14::1a.

aspmx3.googlemail.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.

aspmx.l.google.com resolves to 142.251.163.26 and 2607:f8b0:4004:c09::1b.

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

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

The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 2800:3f0:4003:c14::1a IP addresses.

The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 192.178.234.27 IP addresses.