shellomatic.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`shellomatic.com`

DNSSEC	⚠️ Not signed
A	35.183.136.37^{🇨🇦 Amazon35.182.0.0/15 EC2 YUL prefix}
		PTR	`ec2-35-183-136-37.ca-central-1.compute.amazonaws.com`
NS	`dns2.rebel.com` ⭐
		A	54.200.36.152^{🇺🇸 Amazon54.200.0.0/15 EC2 PDX prefix}
			PTR	`dns2.rebel.com`
		A	54.200.67.125^{🇺🇸 Amazon54.200.0.0/15 EC2 PDX prefix}
			PTR	`dns2.rebel.com`
NS	`dns.rebel.com`
		A	54.236.79.66^{🇺🇸 Amazon54.236.64.0/18 EC2 IAD prefix}
			PTR	`dns.rebel.com`
		A	54.236.227.139^{🇺🇸 Amazon54.236.128.0/17 EC2 IAD prefix}
			PTR	`dns.rebel.com`
MX	`shellomatic-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c942::1^{🇨🇦 Microsoft2a01:111:f000::/36}
			PTR	`mail-yt3pr01cu00701.inbound.protection.outlook.com`
		A	2a01:111:f403:c942::2^{🇨🇦 Microsoft2a01:111:f000::/36}
			PTR	`mail-yt3pr01cu00602.inbound.protection.outlook.com`
		A	2a01:111:f403:c944::^{🇨🇦 Microsoft2a01:111:f000::/36}
			PTR	`mail-yqzpr01cu00900.inbound.protection.outlook.com`
		A	2a01:111:f403:c944::1^{🇨🇦 Microsoft2a01:111:f000::/36}
			PTR	`mail-yqzpr01cu01001.inbound.protection.outlook.com`
		A	52.101.190.1^{🇨🇦 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-yt3pr01cu00701.inbound.protection.outlook.com`
		A	52.101.190.2^{🇨🇦 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-yt3pr01cu00602.inbound.protection.outlook.com`
		A	52.101.190.3^{🇨🇦 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-yt6pr01cu00103.inbound.protection.outlook.com`
		A	52.101.192.0^{🇨🇦 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-yqzpr01cu00900.inbound.protection.outlook.com`
MX	`aspmx.l.google.com`⁽¹⁾
		A	2607:f8b0:4004:c07::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bc-in-f27.1e100.net`
		A	172.253.139.27^{🇺🇸 Google172.253.139.0/24}
			PTR	`yuiadsk-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::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	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.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:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 ip4:70.50.241.235 include:_spf.google.com include:spf.protection.outlo...`
TXT	`MS=C8279665BBEA8A00244439347CD0756E56A872E9`
TXT	`google-site-verification=Jyce0-Ljsn_LAmEtHCOyBK_QV0Yk7MZTXieJ_FbEyRc`
SOA	`dns.rebel.com`noc@rebel.com 2026-09-03 #1

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

Subdomains

www.shellomatic.com

Same first word

shellomatic.com

Similar names

Previous names

Next names

DNS History

20 records (9 active, 11 former)

●NSdns.rebel.com2017-09-18 → 2026-09-03 · 3 obs

○ 2016-09-10 15:08:44
● 2017-09-18 00:49:14
● 2026-09-03 22:01:00

●NSdns2.rebel.com2017-09-18 → 2026-09-03 · 3 obs

○ 2016-09-10 15:08:44
● 2017-09-18 00:49:14
● 2026-09-03 22:01:00

○NSns1.bellhosting.com2007-10-28 → 2007-10-28 · 3 obs

● 2007-10-28 17:22:32
○ 2015-08-13 15:38:26
○ 2026-09-03 22:01:00

○NSns1.meganameservers.com2007-10-28 → 2016-09-10 · 4 obs

● 2007-10-28 17:22:32
● 2016-09-10 15:08:44
○ 2017-09-18 00:49:14
○ 2026-09-03 22:01:00

○NSns2.bellhosting.com2007-10-28 → 2007-10-28 · 3 obs

● 2007-10-28 17:22:32
○ 2015-08-13 15:38:26
○ 2026-09-03 22:01:00

○NSns2.meganameservers.com2007-10-28 → 2016-09-10 · 4 obs

● 2007-10-28 17:22:32
● 2016-09-10 15:08:44
○ 2017-09-18 00:49:14
○ 2026-09-03 22:01:00

○NSns3.meganameservers.com2007-10-28 → 2016-09-10 · 4 obs

● 2007-10-28 17:22:32
● 2016-09-10 15:08:44
○ 2017-09-18 00:49:14
○ 2026-09-03 22:01:00

●MXalt1.aspmx.l.google.com2017-09-18 → 2026-09-03 · 3 obs

○ 2016-09-10 15:08:44
● 2017-09-18 00:49:14
● 2026-09-03 22:01:00

●MXalt2.aspmx.l.google.com2017-09-18 → 2026-09-03 · 3 obs

○ 2016-09-10 15:08:44
● 2017-09-18 00:49:14
● 2026-09-03 22:01:00

●MXalt3.aspmx.l.google.com2017-09-18 → 2026-09-03 · 3 obs

○ 2016-09-10 15:08:44
● 2017-09-18 00:49:14
● 2026-09-03 22:01:00

●MXalt4.aspmx.l.google.com2017-09-18 → 2026-09-03 · 3 obs

○ 2016-09-10 15:08:44
● 2017-09-18 00:49:14
● 2026-09-03 22:01:00

●MXaspmx.l.google.com2017-09-18 → 2026-09-03 · 3 obs

○ 2016-09-10 15:08:44
● 2017-09-18 00:49:14
● 2026-09-03 22:01:00

○MXmx1c9.megamailservers.com2007-10-28 → 2016-09-10 · 4 obs

● 2007-10-28 17:22:32
● 2016-09-10 15:08:44
○ 2017-09-18 00:49:14
○ 2026-09-03 22:01:00

○MXmx2c9.megamailservers.com2007-10-28 → 2016-09-10 · 4 obs

● 2007-10-28 17:22:32
● 2016-09-10 15:08:44
○ 2017-09-18 00:49:14
○ 2026-09-03 22:01:00

○MXmx3c9.megamailservers.com2007-10-28 → 2016-09-10 · 4 obs

● 2007-10-28 17:22:32
● 2016-09-10 15:08:44
○ 2017-09-18 00:49:14
○ 2026-09-03 22:01:00

●MXshellomatic-com.mail.protection.outlook.com2026-02-23 → 2026-09-03 · 3 obs

○ 2017-09-18 00:49:14
● 2026-02-23 20:14:16
● 2026-09-03 22:01:00

○A192.99.114.572017-09-18 → 2017-09-18 · 4 obs

○ 2016-09-10 15:08:44
● 2017-09-18 00:49:14
○ 2026-02-23 20:14:16
○ 2026-09-03 22:01:00

○A199.244.79.622016-09-10 → 2016-09-10 · 4 obs

○ 2016-03-25 11:50:00
● 2016-09-10 15:08:44
○ 2017-09-18 00:49:14
○ 2026-09-03 22:01:00

●A35.183.136.372026-02-23 → 2026-09-03 · 3 obs

○ 2017-09-18 00:49:14
● 2026-02-23 20:14:16
● 2026-09-03 22:01:00

○A69.156.240.292007-10-28 → 2016-03-25 · 4 obs

● 2007-10-28 17:22:32
● 2016-03-25 11:50:00
○ 2016-09-10 15:08:44
○ 2026-09-03 22:01:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, g.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net...	-
shellomatic.com	dns.rebel.com, dns2.rebel.com	2 records

✅ Authoritative Response

Server:54.200.67.125

NS records: dns.rebel.com, dns2.rebel.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for shellomatic.com (unsigned zone)

⏱️ Timing

Total: 556ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`35.183.136.37`
NS	2	`dns.rebel.com, dns2.rebel.com`
MX	6	`ASPMX.L.GOOGLE.com (pri: 1), ALT4.ASPMX.L.GOOGLE.com (pri: 10)...`
TXT	3	`v=spf1 ip4:70.50.241.235 include:_spf.go, MS=C8279665BBEA8A00244439347CD0756E56A87...`
SOA	1	`dns.rebel.com noc.rebel.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns.rebel.com, dns2.rebel.com)

Analysis

Hierarchy

shellomatic.com is the parent zone for www.shellomatic.com.

IP Addresses

shellomatic.com directs to one IP number, which is 35.183.136.37.

Host names like ec2-35-183-136-37.ca-central-1.compute.amazonaws.com are further examples that share IP numbers with shellomatic.com.

Name Servers

Two name servers handle the delegation for shellomatic.com: dns2.rebel.com and dns.rebel.com.

shellomatic.com has the same name server delegation as a number of other domains, such as classdojo.ca, ldfitness.ca, bccraftbrewersguild.com and two more.

shellomatic.com partially shares its NS delegation with several other domains, including academic.ca, proadvisors.ca, internetsolutions.ca and two others.

The name servers dns2.rebel.ca, dns.rebel.ca, dns2.internic.ca and dns.internic.ca are often found in use alongside these name servers.

dns2.rebel.com and dns.rebel.com both carry two IP addresses. The A records for dns2.rebel.com are 54.200.36.152 and 54.200.67.125; the A records for dns.rebel.com are 54.236.79.66 and 54.236.227.139.

Mail Servers

The MX records for shellomatic.com point to 6 mail servers — aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and 3 other.

shellomatic.com shares at least some of its mail servers with other domains — for example gaillowecampaign.com, jacndos.com, obrasrofran.es and two more.

It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.

Host names resolving to 8 IP numbers:

shellomatic-com.mail.protection.outlook.com resolves to 52.101.190.1, 52.101.190.2 and 52.101.190.3 among others, with 5 other IP addresses in total.

Hosts with two IP numbers each:

aspmx.l.google.com resolves to two addresses: 172.253.139.27 and 2607:f8b0:4004:c07::1b.

alt1.aspmx.l.google.com resolves to two addresses: 192.178.234.26 and 2800:3f0:4003:c14::1b.

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

alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.27 and 2a00:1450:400c:c23::1a.