healper.co - robtex.com

Search for stuff

`healper.co`

DNSSEC	⚠️ Not signed
A	3.78.105.135^{🇩🇪 Amazon}
A	63.176.67.239^{🇩🇪 Amazon}
A	63.182.98.89^{🇺🇸 Amazon}
NS	`ns-1982.awsdns-55.co.uk` ⭐
		A	2600:9000:5307:be00::1^{🇺🇸 Amazon}
		A	205.251.199.190^{🇺🇸 Amazon}
NS	`ns-1402.awsdns-47.org`
		A	2600:9000:5305:7a00::1^{🇺🇸 Amazon}
		A	205.251.197.122^{🇺🇸 Amazon}
NS	`ns-24.awsdns-03.com`
		A	2600:9000:5300:1800::1^{🇺🇸 Amazon}
		A	205.251.192.24^{🇺🇸 Amazon}
NS	`ns-601.awsdns-11.net`
		A	2600:9000:5302:5900::1^{🇺🇸 Amazon}
		A	205.251.194.89^{🇺🇸 Amazon}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1f::1b^{🇺🇸 Google}
		A	64.233.180.26^{🇺🇸 Google}
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google}
		A	172.253.116.26^{🇺🇸 Google}
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google}
		A	192.178.223.27^{🇺🇸 Google}
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c00::1b^{🇧🇪 Google}
		A	173.194.76.27^{🇺🇸 Google}
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4025:402::1b^{🇳🇱 Google}
		A	142.250.102.27^{🇺🇸 Google}

`co`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns0.centralnic.net` ⭐ 🔒
	NS	`a.registrydns.co` 🔒
	NS	`b.registrydns.co` 🔒
	NS	`c.registrydns.co` 🔒
	NS	`d.registrydns.co` 🔒

Starts with same word

healper.co

healper.info

healper.dk

healper.com

Starts similarily

alphere.com

ahelper.com

phereal.net

paehler.com

paehler.info

lephare.eu

lephare.jp

halerep.com

healper.info

healper.dk

perheal.com

phereal.com

lephare.co

rephael.co.il

leapehr.com

healper.com

helpear.com

earhelp.net

lephare.com

phealer.net

lephare.nl

helpare.com

epheral.com

pelareh.com

paehler.de

paehler.net

rephael.net

earhelp.co.uk

paehler.eu

lephare.de

healper.co

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
co	a.registrydns.co, b.registrydns.co, c.registrydns.co, d.registrydns.co	8 records
healper.co	ns-1982.awsdns-55.co.uk, ns-1402.awsdns-47.org, ns-24.awsdns-03.com, ns-601.awsdns-11.net	-

✅ Authoritative Response

Server: 2001:500:9f::42

NS records: ns-1982.awsdns-55.co.uk, ns-1402.awsdns-47.org, ns-24.awsdns-03.com, ns-601.awsdns-11.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for healper.co (unsigned zone)

⏱️ Timing

Total: 2222ms | Queries: -

📄 Records

Type	Count	Sample Data
A	3	`63.176.67.239, 63.182.98.89...`
NS	4	`ns-1402.awsdns-47.org, ns-1982.awsdns-55.co.uk...`
MX	5	`aspmx.l.google.com (pri: 0), alt3.aspmx.l.google.com (pri: 10)...`
TXT	1	`google-site-verification=yLqC_1dqpttzMcU`
SOA	1	`ns-1982.awsdns-55.co.uk awsdns-hostmaste`

📌 Glue Records Collected

Total: 8

In-bailiwick: 8 (a.registrydns.co, a.registrydns.co, b.registrydns.co...)

AI analysis

Three IP numbers (3.78.105.135, 63.176.67.239 and 63.182.98.89) are pointed to by healper.co.

Other host names like testing.healper.dk and dev.healper.dk share IP numbers with healper.co.

healper.co is delegated to four name servers: ns-24.awsdns-03.com, ns-601.awsdns-11.net, ns-1402.awsdns-47.org and ns-1982.awsdns-55.co.uk.

healper.co at least partially shares name servers with other domains, for instance d2giid2us3h390.cloudfront.net, wwi.haufe.de, poc.lark.com, ductya-r.com and zahrbockfuneralhome.com.

These name servers are often used together with the name servers ns-1900.awsdns-45.co.uk, ns-981.awsdns-58.net, ns-1448.awsdns-53.org, ns-2036.awsdns-62.co.uk, ns-1198.awsdns-21.org, ns-1944.awsdns-51.co.uk, ns-1491.awsdns-58.org, ns-510.awsdns-63.com, ns-137.awsdns-17.com and ns-900.awsdns-48.net.

Host names with two IP numbers:

Host name ns-24.awsdns-03.com points to: 2600:9000:5300:1800::1 and 205.251.192.24.

Host name ns-601.awsdns-11.net points to: 2600:9000:5302:5900::1 and 205.251.194.89.

Host name ns-1402.awsdns-47.org points to: 2600:9000:5305:7a00::1 and 205.251.197.122.

Host name ns-1982.awsdns-55.co.uk points to: 2600:9000:5307:be00::1 and 205.251.199.190.

healper.co 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.

healper.co shares mail servers with other domains at least partially, including ns500765.ns500693.ns500734.ns500734.ns500693.ns500734.ns500693.ns500734.ns500693.ns500693.ns500693.ns500588.ns500632.ns500110.dtrkdll.com, ns500698.ns500698.ns500759.ns500698.ns500735.ns500735.ns500736.ns500736.ns500698.ns500735.ns500619.ns500619.ns500576.ns500576.trackreceptor.com, ns500671.ns500671.ns500731.ns500754.ns500704.ns500688.ns500671.ns500704.ns500678.ns500688.ns500688.ns500671.ns500649.ns500649.lustychickser.com, ns500671.ns500731.ns500671.ns500731.ns500754.ns500731.ns500704.ns500705.ns500704.ns500666.ns500153.tenderladiesbz.com and ns500724.ns500724.ns500599.ns500737.ns500724.ns500724.ns500724.ns500599.ns500737.ns500599.ns500737.ns500697.ns500599.ns500697.ns500682.ns500669.www.yummyflingsfinder.com.

these mail servers are often used with the mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.

Hosts with two IP numbers:

aspmx.l.google.com points to 2607:f8b0:4004:c1f::1b and 64.233.180.26.

alt1.aspmx.l.google.com points to 2a00:1450:400b:c02::1a and 172.253.116.26.

alt2.aspmx.l.google.com points to 2a00:1450:4009:c0f::1a and 192.178.223.27.

alt3.aspmx.l.google.com points to 2a00:1450:400c:c00::1b and 173.194.76.27.

alt4.aspmx.l.google.com points to 2a00:1450:4025:402::1b and 142.250.102.27.