hypercare.com - dns.ninja

`hypercare.com`

DNSSEC	⚠️ Not signed
A	198.202.211.1^{🇺🇸 CLOUDFLARESPECTRUM198.202.211.0/24 Webflow}
NS	`ns1-01.azure-dns.com` ⭐
		A	2603:1061:0:700::1^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
		A	13.107.236.1^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
NS	`ns2-01.azure-dns.net`
		A	2620:1ec:8ec:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
		A	150.171.21.1^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
NS	`ns3-01.azure-dns.org`
		A	2a01:111:4000:700::1^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-01.azure-dns.org`
		A	204.14.183.1^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-01.azure-dns.org`
NS	`ns4-01.azure-dns.info`
		A	2620:1ec:bda:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
		A	208.84.5.1^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c07::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bc-in-f27.1e100.net`
		A	142.251.163.27^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.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	`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.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 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.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
TXT	`v=spf1 include:_spf.google.com include:stspg-customer.com include:spf.autopil...`
TXT	`google-site-verification=rEZY0dmjf2WUNjBp0reXJhQgubEjsiGEOX0A1ytYaro`
TXT	`MS=A0DAC1F92C3AAA3E24BA0E1D2CFD8851913A2D06`
TXT	`134bc9c9fdad48a58ff1b10fee0a5e2c`
TXT	`sending_domain1104931=6728791aedbc4dae12ffdfb97270c4df913a2f60e7d890dd4bebd8c...`
TXT	`pardot1104931=b5e1d16be88ee1a5b1695fdf2e6ebcb8e039c99b702248f738e2f252ec55d74f`
TXT	`atlassian-domain-verification=I05yf+M28HMdhd9U5SRk6YC878l1anTXvdl5kjFBRSJRFck...`
TXT	`twilio-domain-verification=313e7c80624926753edb224ce58a3a18`
TXT	`status-page-domain-verification=pjzgjf9cxc66`
TXT	`00D8b000002AKKA=1TBJv00000009uX`
SOA	`ns1-01.azure-dns.com`azuredns-hostmaster@microsoft.com serial=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=1783150431

Subdomains

www.hypercare.com

productboard.hypercare.com

Same first word

hypercare.in

hypercare.com

Similar names

hypercrea.com

racephyre.com

DNS History

25 records (10 active, 15 former)

○NSbuy.internettraffic.com2016-03-08 → 2016-06-30 · 5 obs

○ 2015-12-08 07:11:06
● 2016-03-08 17:37:36
● 2016-06-30 10:57:44
○ 2017-03-26 12:53:52
○ 2026-07-04 07:54:00

○NSdns1.name-services.com2015-08-22 → 2015-12-08 · 4 obs

● 2015-08-22 19:21:42
● 2015-12-08 07:11:06
○ 2016-03-08 17:37:36
○ 2026-07-04 07:54:00

○NSdns2.name-services.com2015-08-22 → 2015-12-08 · 4 obs

● 2015-08-22 19:21:42
● 2015-12-08 07:11:06
○ 2016-03-08 17:37:36
○ 2026-07-04 07:54:00

○NSdns3.name-services.com2015-08-22 → 2015-12-08 · 4 obs

● 2015-08-22 19:21:42
● 2015-12-08 07:11:06
○ 2016-03-08 17:37:36
○ 2026-07-04 07:54:00

○NSdns4.name-services.com2015-08-22 → 2015-12-08 · 4 obs

● 2015-08-22 19:21:42
● 2015-12-08 07:11:06
○ 2016-03-08 17:37:36
○ 2026-07-04 07:54:00

○NSdns5.name-services.com2015-08-22 → 2015-12-08 · 4 obs

● 2015-08-22 19:21:42
● 2015-12-08 07:11:06
○ 2016-03-08 17:37:36
○ 2026-07-04 07:54:00

●NSns1-01.azure-dns.com2020-04-10 → 2026-07-04 · 3 obs

○ 2017-03-26 12:53:52
● 2020-04-10 05:05:38
● 2026-07-04 07:54:00

○NSns1.uniregistrymarket.link2017-03-26 → 2017-03-26 · 4 obs

○ 2016-06-30 10:57:44
● 2017-03-26 12:53:52
○ 2020-04-10 05:05:38
○ 2026-07-04 07:54:00

●NSns2-01.azure-dns.net2020-04-10 → 2026-07-04 · 3 obs

○ 2017-03-26 12:53:52
● 2020-04-10 05:05:38
● 2026-07-04 07:54:00

○NSns2.uniregistrymarket.link2017-03-26 → 2017-03-26 · 4 obs

○ 2016-06-30 10:57:44
● 2017-03-26 12:53:52
○ 2020-04-10 05:05:38
○ 2026-07-04 07:54:00

●NSns3-01.azure-dns.org2020-04-10 → 2026-07-04 · 3 obs

○ 2017-03-26 12:53:52
● 2020-04-10 05:05:38
● 2026-07-04 07:54:00

●NSns4-01.azure-dns.info2020-04-10 → 2026-07-04 · 3 obs

○ 2017-03-26 12:53:52
● 2020-04-10 05:05:38
● 2026-07-04 07:54:00

○NSsell.internettraffic.com2016-03-08 → 2016-06-30 · 5 obs

○ 2015-12-08 07:11:06
● 2016-03-08 17:37:36
● 2016-06-30 10:57:44
○ 2017-03-26 12:53:52
○ 2026-07-04 07:54:00

●MXalt1.aspmx.l.google.com2020-04-10 → 2026-07-04 · 3 obs

○ 2016-03-08 17:37:36
● 2020-04-10 05:05:38
● 2026-07-04 07:54:00

●MXalt2.aspmx.l.google.com2020-04-10 → 2026-07-04 · 3 obs

○ 2016-03-08 17:37:36
● 2020-04-10 05:05:38
● 2026-07-04 07:54:00

●MXaspmx.l.google.com2020-04-10 → 2026-07-04 · 3 obs

○ 2016-03-08 17:37:36
● 2020-04-10 05:05:38
● 2026-07-04 07:54:00

●MXaspmx2.googlemail.com2020-04-10 → 2026-07-04 · 3 obs

○ 2016-03-08 17:37:36
● 2020-04-10 05:05:38
● 2026-07-04 07:54:00

●MXaspmx3.googlemail.com2020-04-10 → 2026-07-04 · 3 obs

○ 2016-03-08 17:37:36
● 2020-04-10 05:05:38
● 2026-07-04 07:54:00

○MXp.nsm.ctmail.com2015-08-22 → 2015-12-08 · 4 obs

● 2015-08-22 19:21:42
● 2015-12-08 07:11:06
○ 2016-03-08 17:37:36
○ 2026-07-04 07:54:00

○A104.198.14.522020-04-10 → 2020-04-10 · 4 obs

○ 2017-03-26 12:53:52
● 2020-04-10 05:05:38
○ 2026-02-18 01:37:12
○ 2026-07-04 07:54:00

○A176.74.176.1872017-03-26 → 2017-03-26 · 4 obs

○ 2016-06-30 10:57:44
● 2017-03-26 12:53:52
○ 2020-04-10 05:05:38
○ 2026-07-04 07:54:00

●A198.202.211.12026-02-18 → 2026-07-04 · 3 obs

○ 2020-04-10 05:05:38
● 2026-02-18 01:37:12
● 2026-07-04 07:54:00

○A64.74.223.352015-08-22 → 2015-12-08 · 4 obs

● 2015-08-22 19:21:42
● 2015-12-08 07:11:06
○ 2016-03-08 17:37:36
○ 2026-07-04 07:54:00

○A69.172.201.1532016-06-30 → 2016-06-30 · 4 obs

○ 2016-03-08 17:37:36
● 2016-06-30 10:57:44
○ 2017-03-26 12:53:52
○ 2026-07-04 07:54:00

○A69.172.201.2082016-03-08 → 2016-03-08 · 4 obs

○ 2015-12-08 07:11:06
● 2016-03-08 17:37:36
○ 2016-06-30 10:57:44
○ 2026-07-04 07:54:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, a.gtld-servers.net, d.gtld-servers.net, f.gtld-servers.net...	-
hypercare.com	ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info	2 records

✅ Authoritative Response

Server:208.84.5.1

NS records: ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for hypercare.com (unsigned zone)

⏱️ Timing

Total: 566ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`198.202.211.1`
NS	4	`ns1-01.azure-dns.com, ns2-01.azure-dns.net...`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	10	`v=spf1 include:_spf.google.com include:s, google-site-verification=rEZY0dmjf2WUNjB...`
SOA	1	`ns1-01.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-01.azure-dns.com, ns1-01.azure-dns.com)

Analysis

Hierarchy

www.hypercare.com and productboard.hypercare.com each fall under hypercare.com as their parent domain.

IP Addresses

hypercare.com resolves to just one IP address, 198.202.211.1.

Two other host names, along with digital-touch.de, shiphero.com and autocenter-winkeln.ch, also share IP numbers with hypercare.com.

Name Servers

The NS records for hypercare.com point to four name servers: ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org.

hypercare.com shares at least some of its name servers with other domains, including berlexconnect.com, silverlakeaxis.com, microsoftflightsimulatordownload.net and two others.

The host names ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org each resolve to two IP addresses: ns1-01.azure-dns.com resolves to 13.107.236.1 and 2603:1061:0:700::1; ns4-01.azure-dns.info resolves to 208.84.5.1 and 2620:1ec:bda:700::1; ns2-01.azure-dns.net resolves to 150.171.21.1 and 2620:1ec:8ec:700::1; ns3-01.azure-dns.org resolves to 204.14.183.1 and 2a01:111:4000:700::1.

Mail Servers

hypercare.com 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 hypercare.com and other domains, including ns500758.ns500758.ns500759.ns500758.ns500735.ns500698.ns500698.ns500698.ns500576.ns500576.ns500652.ns500652.trackreceptor.com, outlawadventuretours.com, ns500754.ns500754.ns500731.ns500754.ns500731.ns500671.ns500678.ns500688.ns500678.ns500291.ns500291.ns500153.tenderladiesbz.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 maps to two IP addresses — 108.177.123.27 and 2800:3f0:4003:c0f::1a.

aspmx3.googlemail.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1a.

aspmx.l.google.com maps to two IP addresses — 142.251.163.27 and 2607:f8b0:4004:c07::1b.

alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.27 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1b.

These two host names — aspmx2.googlemail.com and alt1.aspmx.l.google.com — each point to 108.177.123.27 IP addresses.

These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 172.253.116.26 IP addresses.