🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`is4is.com`

DNSSEC	⚠️ Not signed
A	172.190.101.61^{🇺🇸 Microsoft172.160.0.0/11}
		PTR	`cpanel364.turbify.biz`
NS	`ns1.turbify.com` ⭐
		A	20.121.230.119^{🇺🇸 Microsoft20.64.0.0/10}
NS	`ns2.turbify.com`
		A	134.33.240.61^{🇬🇧 Microsoft134.33.0.0/16}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c25::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadtq-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::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.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.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.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.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=bLDPEFEf8LgYfkcWsK9kZAdWFi6laVwaZT-Hp7khxlo`
TXT	`v=spf1 include:_spf.google.com -all`
SOA	`ns1.turbify.com`hostmaster@is4is.com 2026-02-18 #2

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

Same first word

is4is.com

Similar names

4isis.com

is4si.com

DNS History

15 records (8 active, 7 former)

○NShidden-master.yahoo.com2015-07-05 → 2017-04-19 · 4 obs

● 2015-07-05 06:49:06
● 2017-04-19 01:30:30
○ 2026-04-16 12:05:36
○ 2026-08-15 20:47:54

●NSns1.turbify.com2026-04-16 → 2026-08-15 · 3 obs

○ 2017-04-19 01:30:30
● 2026-04-16 12:05:36
● 2026-08-15 20:47:54

●NSns2.turbify.com2026-04-16 → 2026-08-15 · 3 obs

○ 2017-04-19 01:30:30
● 2026-04-16 12:05:36
● 2026-08-15 20:47:54

○NSyns1.yahoo.com2015-07-05 → 2017-04-19 · 4 obs

● 2015-07-05 06:49:06
● 2017-04-19 01:30:30
○ 2026-04-16 12:05:36
○ 2026-08-15 20:47:54

○NSyns2.yahoo.com2015-07-05 → 2017-04-19 · 4 obs

● 2015-07-05 06:49:06
● 2017-04-19 01:30:30
○ 2026-04-16 12:05:36
○ 2026-08-15 20:47:54

●MXalt1.aspmx.l.google.com2026-04-16 → 2026-08-15 · 3 obs

○ 2017-04-19 01:30:30
● 2026-04-16 12:05:36
● 2026-08-15 20:47:54

●MXalt2.aspmx.l.google.com2026-04-16 → 2026-08-15 · 3 obs

○ 2017-04-19 01:30:30
● 2026-04-16 12:05:36
● 2026-08-15 20:47:54

●MXalt3.aspmx.l.google.com2026-04-16 → 2026-08-15 · 3 obs

○ 2017-04-19 01:30:30
● 2026-04-16 12:05:36
● 2026-08-15 20:47:54

●MXalt4.aspmx.l.google.com2026-04-16 → 2026-08-15 · 3 obs

○ 2017-04-19 01:30:30
● 2026-04-16 12:05:36
● 2026-08-15 20:47:54

●MXaspmx.l.google.com2026-04-16 → 2026-08-15 · 3 obs

○ 2017-04-19 01:30:30
● 2026-04-16 12:05:36
● 2026-08-15 20:47:54

○MXmx-biz.mail.am0.yahoodns.net2015-07-05 → 2017-04-19 · 4 obs

● 2015-07-05 06:49:06
● 2017-04-19 01:30:30
○ 2026-04-16 12:05:36
○ 2026-08-15 20:47:54

○A162.144.82.652017-04-19 → 2017-04-19 · 4 obs

○ 2016-05-13 07:18:04
● 2017-04-19 01:30:30
○ 2026-04-16 12:05:36
○ 2026-08-15 20:47:54

●A172.190.101.612026-04-16 → 2026-08-15 · 3 obs

○ 2017-04-19 01:30:30
● 2026-04-16 12:05:36
● 2026-08-15 20:47:54

○A98.139.135.1282015-11-01 → 2016-05-13 · 5 obs

○ 2015-07-05 06:49:06
● 2015-11-01 04:13:42
● 2016-05-13 07:18:04
○ 2017-04-19 01:30:30
○ 2026-08-15 20:47:54

○A98.139.135.1992015-07-05 → 2015-07-05 · 3 obs

● 2015-07-05 06:49:06
○ 2015-11-01 04:13:42
○ 2026-08-15 20:47:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
is4is.com	ns1.turbify.com, ns2.turbify.com	2 records

✅ Authoritative Response

Server:134.33.240.61

NS records: ns1.turbify.com, ns2.turbify.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for is4is.com (unsigned zone)

⏱️ Timing

Total: 100ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`172.190.101.61`
NS	2	`ns2.turbify.com, ns1.turbify.com`
MX	5	`ALT2.ASPMX.L.GOOGLE.com (pri: 5), ALT1.ASPMX.L.GOOGLE.com (pri: 5)...`
TXT	2	`v=spf1 include:_spf.google.com -all, google-site-verification=bLDPEFEf8LgYfkc`
SOA	1	`ns1.turbify.com hostmaster.is4is.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.turbify.com, ns2.turbify.com)

Analysis

IP Addresses

is4is.com points to a single IP number: 172.190.101.61.

Additional host names — executiveparkingservices.com, apsmx.com, china-holly.net and two others — share IP numbers with is4is.com.

Name Servers

DNS delegation for is4is.com points to two name servers: ns1.turbify.com and ns2.turbify.com.

is4is.com shares its name server setup with other domains, including andjgroup.com, scott-sandberg.com, tfsllc.net and two others.

At least some of is4is.com's name servers are shared with other domains, for example ijane.com, tigerkandu.com, glsystemsinc.com and two more.

These name servers tend to be deployed in combination with the name servers yns1.yahoo.com and yns2.yahoo.com.

Each of ns1.turbify.com and ns2.turbify.com has one IP address: ns1.turbify.com uses 20.121.230.119 and ns2.turbify.com uses 134.33.240.61.