operationcare.com - robtex.com

operationcare.com

DNSSEC⚠️ Not signed
A3.33.251.168🇺🇸 Amazon3.33.240.0/20
PTRaec037177372cc6cd.awsglobalaccelerator.com
A15.197.225.128🇺🇸 Amazon15.197.224.0/20
NSns07.domaincontrol.com ⭐
A2603:5:2170::4🇺🇸 GODADDY-DNS2603:5:2170::/44
PTRns07.domaincontrol.com
A97.74.103.4🇺🇸 GODADDY-DNS97.74.102.0/23
PTRns07.domaincontrol.com
NSns08.domaincontrol.com
A2603:5:2270::4🇺🇸 GODADDY-DNS2603:5:2270::/44
PTRns08.domaincontrol.com
A173.201.71.4🇺🇸 GODADDY-DNS173.201.70.0/23
PTRns08.domaincontrol.com
MXaspmx.l.google.com ⭐
A2607:f8b0:4023:c03::1a🇺🇸 Google2607:f8b0::/32
PTRdy-in-f26.1e100.net
A74.125.137.26🇺🇸 Google74.125.137.0/24
PTRdy-in-f26.1e100.net
MXalt1.aspmx.l.google.com(5)
A2800:3f0:4003:c0f::1b🇨🇱 Google2800:3f0:4003::/48
A108.177.123.27🇺🇸 Google108.177.123.0/24
PTRlcscld-in-f27.1e100.net
MXalt2.aspmx.l.google.com(5)
A2607:f8b0:4023:3003::1b🇺🇸 Google2607:f8b0::/32
PTRyulnkjt-in-f27.1e100.net
A172.253.145.27🇺🇸 Google172.253.145.0/24
PTRyulnkjt-in-f27.1e100.net
MXalt3.aspmx.l.google.com(10)
A2a00:1450:4009:c0f::1b🇬🇧 Google2a00:1450:4009::/48
PTRyulhrs-in-f27.1e100.net
A192.178.223.27🇺🇸 Google192.178.223.0/24
PTRyulhrs-in-f27.1e100.net
MXalt4.aspmx.l.google.com(10)
A2a00:1450:400c:c00::1a🇧🇪 Google2a00:1450:400c::/48
PTRws-in-f26.1e100.net
PTRws-in-x1a.1e100.net
A173.194.76.27🇺🇸 Google173.194.76.0/24
PTRws-in-f27.1e100.net
SOAns07.domaincontrol.comdns@jomax.net 2025-08-30 #3

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1776684357

Previously MX for

operationcare.com

Same first word

operationcare.com

DNS History

28 records (9 active, 19 former)

200920112013201520172019202120232025NSns07.domaincontrol.comns08.domaincontrol.comingrid.ns.cloudflare.comivan.ns.cloudflare.comns1.a2hosting.comns2.a2hosting.comns3.a2hosting.comns4.a2hosting.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comdc-e35b8978.operationcare.commx.zoho.commx2.zoho.comoperationcare.comA15.197.225.1283.33.251.168104.28.6.36104.28.7.36104.31.70.71104.31.71.71199.16.172.159199.16.173.1802400:cb00:2048:1::681f:46472400:cb00:2048:1::681f:474774.52.105.210
○NSingrid.ns.cloudflare.com2015-07-07 → 2017-02-10 · 5 obs
○ 2008-03-20 10:03:06
● 2015-07-07 10:50:04
● 2017-02-10 23:31:22
○ 2020-02-02 07:14:18
○ 2026-04-20 11:43:24
○NSivan.ns.cloudflare.com2015-07-07 → 2017-02-10 · 5 obs
○ 2008-03-20 10:03:06
● 2015-07-07 10:50:04
● 2017-02-10 23:31:22
○ 2020-02-02 07:14:18
○ 2026-04-20 11:43:24
●NSns07.domaincontrol.com2026-04-07 → 2026-04-20 · 3 obs
○ 2020-02-02 07:14:18
● 2026-04-07 20:13:26
● 2026-04-20 11:43:24
●NSns08.domaincontrol.com2026-04-07 → 2026-04-20 · 3 obs
○ 2020-02-02 07:14:18
● 2026-04-07 20:13:26
● 2026-04-20 11:43:24
○NSns1.a2hosting.com2020-02-02 → 2020-02-02 · 4 obs
○ 2017-02-10 23:31:22
● 2020-02-02 07:14:18
○ 2026-04-07 20:13:26
○ 2026-04-20 11:43:24
○NSns2.a2hosting.com2020-02-02 → 2020-02-02 · 4 obs
○ 2017-02-10 23:31:22
● 2020-02-02 07:14:18
○ 2026-04-07 20:13:26
○ 2026-04-20 11:43:24
○NSns3.a2hosting.com2020-02-02 → 2020-02-02 · 4 obs
○ 2017-02-10 23:31:22
● 2020-02-02 07:14:18
○ 2026-04-07 20:13:26
○ 2026-04-20 11:43:24
○NSns4.a2hosting.com2020-02-02 → 2020-02-02 · 4 obs
○ 2017-02-10 23:31:22
● 2020-02-02 07:14:18
○ 2026-04-07 20:13:26
○ 2026-04-20 11:43:24
●MXalt1.aspmx.l.google.com2020-02-02 → 2026-04-20 · 3 obs
○ 2017-02-10 23:31:22
● 2020-02-02 07:14:18
● 2026-04-20 11:43:24
●MXalt2.aspmx.l.google.com2020-02-02 → 2026-04-20 · 3 obs
○ 2017-02-10 23:31:22
● 2020-02-02 07:14:18
● 2026-04-20 11:43:24
●MXalt3.aspmx.l.google.com2020-02-02 → 2026-04-20 · 3 obs
○ 2017-02-10 23:31:22
● 2020-02-02 07:14:18
● 2026-04-20 11:43:24
●MXalt4.aspmx.l.google.com2020-02-02 → 2026-04-20 · 3 obs
○ 2017-02-10 23:31:22
● 2020-02-02 07:14:18
● 2026-04-20 11:43:24
●MXaspmx.l.google.com2020-02-02 → 2026-04-20 · 3 obs
○ 2017-02-10 23:31:22
● 2020-02-02 07:14:18
● 2026-04-20 11:43:24
○MXdc-e35b8978.operationcare.com2016-02-08 → 2016-05-01 · 5 obs
○ 2015-07-07 10:50:04
● 2016-02-08 18:30:56
● 2016-05-01 15:27:54
○ 2017-02-10 23:31:22
○ 2026-04-20 11:43:24
○MXmx.zoho.com2017-02-10 → 2017-02-10 · 4 obs
○ 2016-05-01 15:27:54
● 2017-02-10 23:31:22
○ 2020-02-02 07:14:18
○ 2026-04-20 11:43:24
○MXmx2.zoho.com2017-02-10 → 2017-02-10 · 4 obs
○ 2016-05-01 15:27:54
● 2017-02-10 23:31:22
○ 2020-02-02 07:14:18
○ 2026-04-20 11:43:24
○MXoperationcare.com2008-03-20 → 2008-03-20 · 3 obs
● 2008-03-20 10:03:06
○ 2015-07-07 10:50:04
○ 2026-04-20 11:43:24
○A104.28.6.362015-11-11 → 2016-05-01 · 5 obs
○ 2015-07-07 10:50:04
● 2015-11-11 14:55:36
● 2016-05-01 15:27:54
○ 2017-02-10 23:31:22
○ 2026-04-20 11:43:24
○A104.28.7.362015-11-11 → 2016-05-01 · 5 obs
○ 2015-07-07 10:50:04
● 2015-11-11 14:55:36
● 2016-05-01 15:27:54
○ 2017-02-10 23:31:22
○ 2026-04-20 11:43:24
○A104.31.70.712017-02-10 → 2017-02-10 · 4 obs
○ 2016-05-01 15:27:54
● 2017-02-10 23:31:22
○ 2020-02-02 07:14:18
○ 2026-04-20 11:43:24
○A104.31.71.712017-02-10 → 2017-02-10 · 4 obs
○ 2016-05-01 15:27:54
● 2017-02-10 23:31:22
○ 2020-02-02 07:14:18
○ 2026-04-20 11:43:24
●A15.197.225.1282026-04-07 → 2026-04-20 · 3 obs
○ 2020-02-02 07:14:18
● 2026-04-07 20:13:26
● 2026-04-20 11:43:24
○A199.16.172.1592020-02-02 → 2020-02-02 · 4 obs
○ 2017-02-10 23:31:22
● 2020-02-02 07:14:18
○ 2026-04-07 20:13:26
○ 2026-04-20 11:43:24
○A199.16.173.1802020-02-02 → 2020-02-02 · 4 obs
○ 2017-02-10 23:31:22
● 2020-02-02 07:14:18
○ 2026-04-07 20:13:26
○ 2026-04-20 11:43:24
○A2400:cb00:2048:1::681f:46472017-02-10 → 2017-02-10 · 4 obs
○ 2016-05-01 15:27:54
● 2017-02-10 23:31:22
○ 2020-02-02 07:14:18
○ 2026-04-20 11:43:24
○A2400:cb00:2048:1::681f:47472017-02-10 → 2017-02-10 · 4 obs
○ 2016-05-01 15:27:54
● 2017-02-10 23:31:22
○ 2020-02-02 07:14:18
○ 2026-04-20 11:43:24
●A3.33.251.1682026-04-07 → 2026-04-20 · 3 obs
○ 2020-02-02 07:14:18
● 2026-04-07 20:13:26
● 2026-04-20 11:43:24
○A74.52.105.2102008-03-20 → 2008-03-20 · 3 obs
● 2008-03-20 10:03:06
○ 2015-07-07 10:50:04
○ 2026-04-20 11:43:24

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comb.gtld-servers.net, i.gtld-servers.net, f.gtld-servers.net, k.gtld-servers.net...-
operationcare.comns07.domaincontrol.com, ns08.domaincontrol.com4 records

✅ Authoritative Response

Server:173.201.71.4

NS records: ns07.domaincontrol.com, ns08.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for operationcare.com (unsigned zone)

⏱️ Timing

Total: 418ms | Queries: -

📄 Records

TypeCountSample Data
A215.197.225.128, 3.33.251.168
NS2ns07.domaincontrol.com, ns08.domaincontrol.com
MX5alt3.aspmx.l.google.com (pri: 10), alt4.aspmx.l.google.com (pri: 10)...
SOA1ns07.domaincontrol.com dns.jomax.net

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns07.domaincontrol.com, ns07.domaincontrol.com, ns08.domaincontrol.com...)

Analysis

IP Addresses

operationcare.com points to two IP numbers: 3.33.251.168 and 15.197.225.128.

Other host names such as scrollfiends.com, northwestmedicalassociates.com, rigolets.net, langsec.com and betterfatloss.com share IP numbers with operationcare.com.

Name Servers

operationcare.com is delegated to two name servers: ns07.domaincontrol.com and ns08.domaincontrol.com.

operationcare.com uses the same name server setup as other domains, including kjpdzh.ch, fjlart.com, growingps.com, davebenham.net and sciopro.com.

Host names with two IP numbers:

ns07.domaincontrol.com points to 2603:5:2170::4 and 97.74.103.4.

ns08.domaincontrol.com points to 2603:5:2270::4 and 173.201.71.4.

Mail Servers

operationcare.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.

operationcare.com shares at least some mail servers with other domains, for example ns500734.ns500699.ns500734.ns500699.ns500699.ns500699.ns500588.ns500699.ns500699.ns500588.ns500699.ns500693.ns500632.ns500612.ns500110.dtrkdll.com, ns500759.ns500758.ns500698.ns500758.ns500736.ns500735.ns500736.ns500708.ns500698.ns500619.ns500576.ns500576.ns500652.trackreceptor.com, ns500671.ns500731.ns500671.ns500704.ns500671.ns500671.ns500705.ns500704.ns500688.ns500671.ns500649.ns500649.ns500649.ns500153.tenderladiesbz.com, ns500759.ns500759.ns500759.ns500698.ns500736.ns500698.ns500576.ns500576.ns500708.ns500708.ns500576.ns500619.ns500652.ns500619.trackreceptor.com and ns500734.ns500693.ns500693.ns500693.ns500699.ns500734.ns500588.ns500693.ns500693.ns500588.ns500693.ns500612.ns500588.ns500588.ns500612.ns500588.ns500588.dtrkdll.com.

These mail servers are commonly used alongside aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.

Host names with two IP numbers: aspmx.l.google.com points to 2607:f8b0:4023:c03::1a and 74.125.137.26; alt1.aspmx.l.google.com points to 2800:3f0:4003:c0f::1b and 108.177.123.27; alt2.aspmx.l.google.com points to 2607:f8b0:4023:3003::1b and 172.253.145.27; alt3.aspmx.l.google.com points to 2a00:1450:4009:c0f::1b and 192.178.223.27; alt4.aspmx.l.google.com points to 2a00:1450:400c:c00::1a and 173.194.76.27.