helimed.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`helimed.com`

DNSSEC	⚠️ Not signed
A	66.45.246.141^{🇺🇸 NJIIX-166.45.224.0/19 NJIIX.net 110B Meadowlands Pkwy Secaucus, NJ 07094}
NS	`ns1.domainrecover.com` ⭐ ⚠️ Not in parent delegation
		A	149.248.38.58^{🇺🇸 AS-VULTR149.248.32.0/20 Vultr Assigned Prefix}
			PTR	`149.248.38.58.vultrusercontent.com`
NS	`ns.servering.com` ⚠️ Not in zone NS records
		A	199.247.16.62^{🇩🇪 AS-VULTR199.247.16.0/21 Vultr Assigned Prefix}
			PTR	`199.247.16.62.vultrusercontent.com`
NS	`ns2.domainrecover.com` ⚠️ Not in parent delegation
		A	199.247.16.62^{🇩🇪 AS-VULTR199.247.16.0/21 Vultr Assigned Prefix}
			PTR	`199.247.16.62.vultrusercontent.com`
NS	`ns2.servering.com` ⚠️ Not in zone NS records
		A	149.248.38.58^{🇺🇸 AS-VULTR149.248.32.0/20 Vultr Assigned Prefix}
			PTR	`149.248.38.58.vultrusercontent.com`
TXT	`yGjyZf7SHD`
SOA	`ns1.domainrecover.com`hostmaster@domainreover.com serial=1623031840

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

Same first word

helimed.de

helimed.pl

helimed.cl

helimed.com

helimed.com.br

helimed.aero

Similar names

delhime.com

eldheim.com

edlheim.de

delheim.com

elmehdi.com

heilmed.com

medihel.com.cn

helidem.de

medheli.com

delheim.co.za

helmdie.de

DNS History

13 records (5 active, 8 former)

●NSns.servering.com2026-03-23 → 2026-08-15 · 3 obs

○ 2017-11-14 10:40:42
● 2026-03-23 16:48:42
● 2026-08-15 21:27:18

●NSns1.domainrecover.com2026-03-23 → 2026-08-15 · 3 obs

○ 2017-11-14 10:40:42
● 2026-03-23 16:48:42
● 2026-08-15 21:27:18

○NSns1.dsredirection.com2015-11-12 → 2016-12-27 · 4 obs

● 2015-11-12 15:06:18
● 2016-12-27 03:56:34
○ 2017-11-14 10:40:42
○ 2026-08-15 21:27:18

●NSns2.domainrecover.com2026-03-23 → 2026-08-15 · 3 obs

○ 2017-11-14 10:40:42
● 2026-03-23 16:48:42
● 2026-08-15 21:27:18

○NSns2.dsredirection.com2015-11-12 → 2016-12-27 · 4 obs

● 2015-11-12 15:06:18
● 2016-12-27 03:56:34
○ 2017-11-14 10:40:42
○ 2026-08-15 21:27:18

●NSns2.servering.com2026-03-23 → 2026-08-15 · 3 obs

○ 2017-11-14 10:40:42
● 2026-03-23 16:48:42
● 2026-08-15 21:27:18

○MXmxs1.domainrecover.com2015-07-14 → 2017-11-14 · 4 obs

● 2015-07-14 08:29:56
● 2017-11-14 10:40:42
○ 2026-03-23 16:48:42
○ 2026-08-15 21:27:18

○MXmxs2.domainrecover.com2015-07-14 → 2017-11-14 · 4 obs

● 2015-07-14 08:29:56
● 2017-11-14 10:40:42
○ 2026-03-23 16:48:42
○ 2026-08-15 21:27:18

○A141.8.230.202015-07-14 → 2016-12-27 · 4 obs

● 2015-07-14 08:29:56
● 2016-12-27 03:56:34
○ 2017-11-14 10:40:42
○ 2026-08-15 21:27:18

●A66.45.246.1412026-03-23 → 2026-08-15 · 3 obs

○ 2017-11-14 10:40:42
● 2026-03-23 16:48:42
● 2026-08-15 21:27:18

○CNAMEpres.serverhome.com2015-07-14 → 2017-11-14 · 4 obs

● 2015-07-14 08:29:56
● 2017-11-14 10:40:42
○ 2026-03-23 16:48:42
○ 2026-08-15 21:27:18

○CNAMEthie5ku9.dsgeneration.com2015-11-12 → 2016-12-27 · 5 obs

○ 2015-07-14 08:29:56
● 2015-11-12 15:06:18
● 2016-12-27 03:56:34
○ 2017-11-14 10:40:42
○ 2026-08-15 21:27:18

○PTRns1.dsredirection.com2016-12-27 → 2016-12-27 · 3 obs

● 2016-12-27 03:56:34
○ 2017-11-14 10:40:42
○ 2026-08-15 21:27:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
helimed.com	ns.servering.com, ns2.servering.com	2 records

✅ Authoritative Response

Server:149.248.38.58

NS records: ns.servering.com, ns2.servering.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for helimed.com (unsigned zone)

⏱️ Timing

Total: 267ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`66.45.246.141`
NS	2	`NS2.DOMAINRECOVER.com, NS1.DOMAINRECOVER.com`
TXT	1	`yGjyZf7SHD`
SOA	1	`ns1.domainrecover.com hostmaster.domainr`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns.servering.com, ns2.servering.com)

Analysis

IP Addresses

helimed.com points to a single IP number: 66.45.246.141.

Additional host names — roris.com, proempresa.com, polrus.com and two others — share IP numbers with helimed.com.

Name Servers

helimed.com has four authoritative name servers: ns1.domainrecover.com, ns2.domainrecover.com, ns2.servering.com and ns.servering.com.

The name servers of helimed.com overlap at least partially with those of other domains — among them keyfor.com, eshko.com, be-k.com and two more.

These name servers commonly appear alongside the name servers ns1.serverhome.com and ns2.serverhome.com.

Each of the host names ns1.domainrecover.com, ns2.domainrecover.com, ns2.servering.com and ns.servering.com has one IP address: ns1.domainrecover.com resolves to 149.248.38.58, ns2.domainrecover.com resolves to 199.247.16.62, ns2.servering.com resolves to 149.248.38.58 and ns.servering.com resolves to 199.247.16.62.

ns1.domainrecover.com along with ns2.servering.com each resolve to 149.248.38.58 IP addresses.

ns2.domainrecover.com along with ns.servering.com each resolve to 199.247.16.62 IP addresses.