redservice.com.mx - dns.ninja

`redservice.com.mx`

DNSSEC	⚠️ Not signed
A	2606:4700:3033::ac43:a4ac^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::6815:3ad1^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.58.209^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.164.172^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`ara.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a43^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ara.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c043^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ara.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2043^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ara.ns.cloudflare.com`
		A	108.162.192.67^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ara.ns.cloudflare.com`
		A	172.64.32.67^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ara.ns.cloudflare.com`
		A	173.245.58.67^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ara.ns.cloudflare.com`
NS	`kevin.ns.cloudflare.com`
		A	2606:4700:58::adf5:3bbf^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kevin.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1bf^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kevin.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21bf^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kevin.ns.cloudflare.com`
		A	108.162.193.191^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kevin.ns.cloudflare.com`
		A	172.64.33.191^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kevin.ns.cloudflare.com`
		A	173.245.59.191^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kevin.ns.cloudflare.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c21::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pe-in-f27.1e100.net`
		A	172.253.122.27^{🇺🇸 Google172.253.122.0/24}
			PTR	`bh-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽¹⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-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.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽²⁰⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-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.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.58.209, 172.67.164.172
		IPv6 hints	2606:4700:3033::ac43:a4ac, 2606:4700:3036::6815:3ad1
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=86, name=cloudflare-ech.com
SOA	`ara.ns.cloudflare.com`dns@cloudflare.com serial=2407570575

`com.mx`

	DNSSEC	⚠️ Not signed
	NS	`m.mx-ns.mx` ⭐ ⚠️ Not in parent delegation
	NS	`c.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`e.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`i.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`o.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`x.mx-ns.mx` ⚠️ Not in parent delegation
	TXT	`v=spf1 -all`
	SOA	`m.mx-ns.mx`hostmaster@nic.mx serial=1783151524

WOT: NOT_SAFE (44/100)

Same first word

redservice.com.au

redservice.org

redservice.com.mx

redservice.cc

redservice.com

redservice.net

redservice.su

redservice.com.br

Similar names

DNS History

22 records (11 active, 11 former)

●NSara.ns.cloudflare.com2026-02-24 → 2026-07-04 · 3 obs

○ 2018-10-04 07:07:52
● 2026-02-24 03:43:56
● 2026-07-04 08:07:06

●NSkevin.ns.cloudflare.com2026-02-24 → 2026-07-04 · 3 obs

○ 2018-10-04 07:07:52
● 2026-02-24 03:43:56
● 2026-07-04 08:07:06

○NSns1.inovecom.mx2017-02-05 → 2018-10-04 · 5 obs

○ 2016-03-01 00:38:46
● 2017-02-05 06:29:14
● 2018-10-04 07:07:52
○ 2026-02-24 03:43:56
○ 2026-07-04 08:07:06

○NSns1.ipage.com2015-07-25 → 2016-03-01 · 4 obs

● 2015-07-25 01:37:22
● 2016-03-01 00:38:46
○ 2017-02-05 06:29:14
○ 2026-07-04 08:07:06

○NSns2.inovecom.mx2017-02-05 → 2018-10-04 · 5 obs

○ 2016-03-01 00:38:46
● 2017-02-05 06:29:14
● 2018-10-04 07:07:52
○ 2026-02-24 03:43:56
○ 2026-07-04 08:07:06

○NSns2.ipage.com2015-07-25 → 2016-03-01 · 4 obs

● 2015-07-25 01:37:22
● 2016-03-01 00:38:46
○ 2017-02-05 06:29:14
○ 2026-07-04 08:07:06

●MXalt1.aspmx.l.google.com2015-07-25 → 2026-07-04 · 2 obs

● 2015-07-25 01:37:22
● 2026-07-04 08:07:06

●MXalt2.aspmx.l.google.com2015-07-25 → 2026-07-04 · 2 obs

● 2015-07-25 01:37:22
● 2026-07-04 08:07:06

●MXaspmx.l.google.com2015-07-25 → 2026-07-04 · 2 obs

● 2015-07-25 01:37:22
● 2026-07-04 08:07:06

●MXaspmx2.googlemail.com2015-07-25 → 2026-07-04 · 2 obs

● 2015-07-25 01:37:22
● 2026-07-04 08:07:06

●MXaspmx3.googlemail.com2015-07-25 → 2026-07-04 · 2 obs

● 2015-07-25 01:37:22
● 2026-07-04 08:07:06

●A104.21.58.2092026-02-24 → 2026-07-04 · 6 obs

○ 2018-10-04 07:07:52
● 2026-02-24 03:43:56
○ 2026-02-26 03:05:50
○ 2026-03-17 16:09:32
● 2026-06-09 13:05:36
● 2026-07-04 08:07:06

●A172.67.164.1722026-02-24 → 2026-07-04 · 6 obs

○ 2018-10-04 07:07:52
● 2026-02-24 03:43:56
○ 2026-02-26 03:05:50
○ 2026-03-17 16:09:32
● 2026-06-09 13:05:36
● 2026-07-04 08:07:06

○A188.114.96.02026-02-26 → 2026-03-17 · 5 obs

○ 2026-02-24 03:43:56
● 2026-02-26 03:05:50
● 2026-03-17 16:09:32
○ 2026-06-09 13:05:36
○ 2026-07-04 08:07:06

○A188.114.97.02026-02-26 → 2026-03-17 · 5 obs

○ 2026-02-24 03:43:56
● 2026-02-26 03:05:50
● 2026-03-17 16:09:32
○ 2026-06-09 13:05:36
○ 2026-07-04 08:07:06

●A2606:4700:3033::ac43:a4ac2026-02-24 → 2026-07-04 · 6 obs

○ 2018-10-04 07:07:52
● 2026-02-24 03:43:56
○ 2026-02-26 03:05:50
○ 2026-03-17 16:09:32
● 2026-06-09 13:05:36
● 2026-07-04 08:07:06

●A2606:4700:3036::6815:3ad12026-02-24 → 2026-07-04 · 6 obs

○ 2018-10-04 07:07:52
● 2026-02-24 03:43:56
○ 2026-02-26 03:05:50
○ 2026-03-17 16:09:32
● 2026-06-09 13:05:36
● 2026-07-04 08:07:06

○A2a06:98c1:3120::2026-02-26 → 2026-03-17 · 5 obs

○ 2026-02-24 03:43:56
● 2026-02-26 03:05:50
● 2026-03-17 16:09:32
○ 2026-06-09 13:05:36
○ 2026-07-04 08:07:06

○A2a06:98c1:3121::2026-02-26 → 2026-03-17 · 5 obs

○ 2026-02-24 03:43:56
● 2026-02-26 03:05:50
● 2026-03-17 16:09:32
○ 2026-06-09 13:05:36
○ 2026-07-04 08:07:06

○A66.96.147.1102015-07-25 → 2015-11-18 · 4 obs

● 2015-07-25 01:37:22
● 2015-11-18 17:44:24
○ 2016-03-01 00:38:46
○ 2026-07-04 08:07:06

○A66.96.149.322016-03-01 → 2016-03-01 · 4 obs

○ 2015-11-18 17:44:24
● 2016-03-01 00:38:46
○ 2017-02-05 06:29:14
○ 2026-07-04 08:07:06

○A67.222.10.1872017-02-05 → 2018-10-04 · 5 obs

○ 2016-03-01 00:38:46
● 2017-02-05 06:29:14
● 2018-10-04 07:07:52
○ 2026-02-24 03:43:56
○ 2026-07-04 08:07:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx...	-
redservice.com.mx	ara.ns.cloudflare.com, kevin.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.33.191

NS records: ara.ns.cloudflare.com, kevin.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for redservice.com.mx (unsigned zone)

⏱️ Timing

Total: 515ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.164.172, 104.21.58.209`
AAAA	2	`2606:4700:3033::ac43:a4ac, 2606:4700:3036::6815:3ad1`
NS	2	`ara.ns.cloudflare.com, kevin.ns.cloudflare.com`
MX	5	`aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 15)...`
TXT	1	`v=spf1 include:_spf.google.com ~all`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`ara.ns.cloudflare.com dns.cloudflare.com`

Analysis

IP Addresses

redservice.com.mx resolves to four IP addresses: 104.21.58.209, 172.67.164.172, 2606:4700:3033::ac43:a4ac and 2606:4700:3036::6815:3ad1.

Two other host names, along with mail.projectbriefs.com, www.nexfar.com.br and etsy-verify.sbs, also share IP numbers with redservice.com.mx.

Name Servers

redservice.com.mx uses two name servers for its delegation: ara.ns.cloudflare.com and kevin.ns.cloudflare.com.

redservice.com.mx shares its NS records with other domains, for example lbg-cp.com, melumatlar.az, 8181.ca and two others.

redservice.com.mx has at least partial name server overlap with other domains, such as bethelweb.com.hk, youtubesokuho.com, ylqhealth.com and two others.

It is common to see these name servers used together with name servers cameron.ns.cloudflare.com and sri.ns.cloudflare.com.

DNS names with 6 IP addresses:

Hostname ara.ns.cloudflare.com directs to 108.162.192.67, 172.64.32.67 and 173.245.58.67 along with 3 other IP addresses.

Hostname kevin.ns.cloudflare.com directs to 108.162.193.191, 172.64.33.191 and 173.245.59.191 along with 3 other IP addresses.

Mail Servers

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

There is at least a partial MX overlap between redservice.com.mx and other domains, including ns500671.ns500671.ns500731.ns500731.ns500671.ns500742.ns500704.ns500688.ns500678.ns500704.ns500678.ns500688.tenderladiesbz.com, ns500759.ns500759.ns500698.ns500759.ns500758.ns500698.ns500735.ns500698.ns500736.ns500698.ns500698.ns500708.ns500576.ns500686.ns500576.ns500619.ns500619.trackreceptor.com, dralexvasserman.com and two others.

These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.

Host names that have two IP addresses:

aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.

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

aspmx.l.google.com directs traffic to 172.253.122.27 and 2607:f8b0:4004:c21::1b.

alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.

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

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.

Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.