hypercard.com - dns.ninja

`hypercard.com`

DNSSEC	⚠️ Not signed
A	198.202.211.1^{🇺🇸 CLOUDFLARESPECTRUM198.202.211.0/24 Webflow}
NS	`ns-1780.awsdns-30.co.uk` ⭐
		A	2600:9000:5306:f400::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1780.awsdns-30.co.uk`
		A	205.251.198.244^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1780.awsdns-30.co.uk`
NS	`ns-1448.awsdns-53.org`
		A	2600:9000:5305:a800::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1448.awsdns-53.org`
		A	205.251.197.168^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1448.awsdns-53.org`
NS	`ns-792.awsdns-35.net`
		A	2600:9000:5303:1800::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-792.awsdns-35.net`
		A	205.251.195.24^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-792.awsdns-35.net`
NS	`ns-95.awsdns-11.com`
		A	2600:9000:5300:5f00::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-95.awsdns-11.com`
		A	205.251.192.95^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-95.awsdns-11.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c17::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f26.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 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	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`MS=ms16245278`
TXT	`google-site-verification=ThHbsu0HIdsSVwL6d6jskD6QfTOslB0aBeHdKekfLNw`
TXT	`google-site-verification=hN9M99yIXiXtic9NUxo_WwPK_06H8FjGRgWv3E0NI24`
TXT	`proxy-ssl.webflow.com`
TXT	`v=spf1 include:_spf.google.com -all`
SOA	`ns-1780.awsdns-30.co.uk`awsdns-hostmaster@amazon.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=1785837987

Same first word

hypercard.com.cn

hypercard.net

hypercard.com

hypercard.info

hypercard.org

Similar names

pdarchery.com

pharrcyde.com

chadperry.com

DNS History

28 records (10 active, 18 former)

●NSns-1448.awsdns-53.org2026-02-24 → 2026-08-04 · 3 obs

○ 2018-06-29 12:56:14
● 2026-02-24 14:13:12
● 2026-08-04 10:33:28

●NSns-1780.awsdns-30.co.uk2026-02-24 → 2026-08-04 · 3 obs

○ 2018-06-29 12:56:14
● 2026-02-24 14:13:12
● 2026-08-04 10:33:28

●NSns-792.awsdns-35.net2026-02-24 → 2026-08-04 · 3 obs

○ 2018-06-29 12:56:14
● 2026-02-24 14:13:12
● 2026-08-04 10:33:28

●NSns-95.awsdns-11.com2026-02-24 → 2026-08-04 · 3 obs

○ 2018-06-29 12:56:14
● 2026-02-24 14:13:12
● 2026-08-04 10:33:28

○NSns-cloud-a1.googledomains.com2018-06-29 → 2018-06-29 · 4 obs

○ 2017-01-11 06:05:46
● 2018-06-29 12:56:14
○ 2026-02-24 14:13:12
○ 2026-08-04 10:33:28

○NSns-cloud-a2.googledomains.com2018-06-29 → 2018-06-29 · 4 obs

○ 2017-01-11 06:05:46
● 2018-06-29 12:56:14
○ 2026-02-24 14:13:12
○ 2026-08-04 10:33:28

○NSns-cloud-a3.googledomains.com2018-06-29 → 2018-06-29 · 4 obs

○ 2017-01-11 06:05:46
● 2018-06-29 12:56:14
○ 2026-02-24 14:13:12
○ 2026-08-04 10:33:28

○NSns-cloud-a4.googledomains.com2018-06-29 → 2018-06-29 · 4 obs

○ 2017-01-11 06:05:46
● 2018-06-29 12:56:14
○ 2026-02-24 14:13:12
○ 2026-08-04 10:33:28

○NSns13.domaincontrol.com2015-07-14 → 2017-01-11 · 4 obs

● 2015-07-14 06:06:52
● 2017-01-11 06:05:46
○ 2018-06-29 12:56:14
○ 2026-08-04 10:33:28

○NSns14.domaincontrol.com2015-07-14 → 2017-01-11 · 4 obs

● 2015-07-14 06:06:52
● 2017-01-11 06:05:46
○ 2018-06-29 12:56:14
○ 2026-08-04 10:33:28

●MXalt1.aspmx.l.google.com2026-02-24 → 2026-08-04 · 3 obs

○ 2018-06-29 12:56:14
● 2026-02-24 14:13:12
● 2026-08-04 10:33:28

●MXalt2.aspmx.l.google.com2026-02-24 → 2026-08-04 · 3 obs

○ 2018-06-29 12:56:14
● 2026-02-24 14:13:12
● 2026-08-04 10:33:28

●MXalt3.aspmx.l.google.com2026-02-24 → 2026-08-04 · 3 obs

○ 2018-06-29 12:56:14
● 2026-02-24 14:13:12
● 2026-08-04 10:33:28

●MXalt4.aspmx.l.google.com2026-02-24 → 2026-08-04 · 3 obs

○ 2018-06-29 12:56:14
● 2026-02-24 14:13:12
● 2026-08-04 10:33:28

●MXaspmx.l.google.com2026-02-24 → 2026-08-04 · 3 obs

○ 2018-06-29 12:56:14
● 2026-02-24 14:13:12
● 2026-08-04 10:33:28

○MXmailstore1.secureserver.net2015-07-14 → 2017-01-11 · 4 obs

● 2015-07-14 06:06:52
● 2017-01-11 06:05:46
○ 2018-06-29 12:56:14
○ 2026-08-04 10:33:28

○MXsmtp.secureserver.net2015-07-14 → 2017-01-11 · 4 obs

● 2015-07-14 06:06:52
● 2017-01-11 06:05:46
○ 2018-06-29 12:56:14
○ 2026-08-04 10:33:28

○A184.168.221.262015-07-14 → 2016-05-04 · 4 obs

● 2015-07-14 06:06:52
● 2016-05-04 11:17:08
○ 2017-01-11 06:05:46
○ 2026-08-04 10:33:28

○A184.168.221.282017-01-11 → 2017-01-11 · 4 obs

○ 2016-05-04 11:17:08
● 2017-01-11 06:05:46
○ 2018-06-29 12:56:14
○ 2026-08-04 10:33:28

●A198.202.211.12026-02-24 → 2026-08-04 · 3 obs

○ 2018-06-29 12:56:14
● 2026-02-24 14:13:12
● 2026-08-04 10:33:28

○A2001:4860:4802:32::152018-06-29 → 2018-06-29 · 4 obs

○ 2017-01-11 06:05:46
● 2018-06-29 12:56:14
○ 2026-02-24 14:13:12
○ 2026-08-04 10:33:28

○A2001:4860:4802:34::152018-06-29 → 2018-06-29 · 4 obs

○ 2017-01-11 06:05:46
● 2018-06-29 12:56:14
○ 2026-02-24 14:13:12
○ 2026-08-04 10:33:28

○A2001:4860:4802:36::152018-06-29 → 2018-06-29 · 4 obs

○ 2017-01-11 06:05:46
● 2018-06-29 12:56:14
○ 2026-02-24 14:13:12
○ 2026-08-04 10:33:28

○A2001:4860:4802:38::152018-06-29 → 2018-06-29 · 4 obs

○ 2017-01-11 06:05:46
● 2018-06-29 12:56:14
○ 2026-02-24 14:13:12
○ 2026-08-04 10:33:28

○A216.239.32.212018-06-29 → 2018-06-29 · 4 obs

○ 2017-01-11 06:05:46
● 2018-06-29 12:56:14
○ 2026-02-24 14:13:12
○ 2026-08-04 10:33:28

○A216.239.34.212018-06-29 → 2018-06-29 · 4 obs

○ 2017-01-11 06:05:46
● 2018-06-29 12:56:14
○ 2026-02-24 14:13:12
○ 2026-08-04 10:33:28

○A216.239.36.212018-06-29 → 2018-06-29 · 4 obs

○ 2017-01-11 06:05:46
● 2018-06-29 12:56:14
○ 2026-02-24 14:13:12
○ 2026-08-04 10:33:28

○A216.239.38.212018-06-29 → 2018-06-29 · 4 obs

○ 2017-01-11 06:05:46
● 2018-06-29 12:56:14
○ 2026-02-24 14:13:12
○ 2026-08-04 10:33:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
hypercard.com	ns-95.awsdns-11.com, ns-792.awsdns-35.net, ns-1780.awsdns-30.co.uk, ns-1448.awsdns-53.org	2 records

✅ Authoritative Response

Server:205.251.197.168

NS records: ns-95.awsdns-11.com, ns-792.awsdns-35.net, ns-1780.awsdns-30.co.uk, ns-1448.awsdns-53.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for hypercard.com (unsigned zone)

⏱️ Timing

Total: 434ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`198.202.211.1`
NS	4	`ns-1448.awsdns-53.org, ns-1780.awsdns-30.co.uk...`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	5	`MS=ms16245278, google-site-verification=ThHbsu0HIdsSVwL...`
SOA	1	`ns-1780.awsdns-30.co.uk awsdns-hostmaste`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-95.awsdns-11.com, ns-95.awsdns-11.com)

Analysis

IP Addresses

hypercard.com points to a single IP number: 198.202.211.1.

Additional host names — ginaannetaylor.com, lagrangefoundation.org, aerolane.com and two others — share IP numbers with hypercard.com.

Name Servers

hypercard.com has four authoritative name servers: ns-95.awsdns-11.com, ns-792.awsdns-35.net, ns-1448.awsdns-53.org and ns-1780.awsdns-30.co.uk.

At least some of hypercard.com's name servers are shared with other domains, for example continuousbuzz.com, fixura.at, timmccahan.com and two more.

It is common for these name servers to be used in conjunction with the name servers ns-24.awsdns-03.com, ns-981.awsdns-58.net and ns-1900.awsdns-45.co.uk.

Four hostnames, each resolving to a pair of IP addresses: ns-95.awsdns-11.com directs to 205.251.192.95 and 2600:9000:5300:5f00::1; ns-792.awsdns-35.net directs to 205.251.195.24 and 2600:9000:5303:1800::1; ns-1448.awsdns-53.org directs to 205.251.197.168 and 2600:9000:5305:a800::1; ns-1780.awsdns-30.co.uk directs to 205.251.198.244 and 2600:9000:5306:f400::1.

Mail Servers

Five mail servers handle hypercard.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

hypercard.com shares mail servers — at least in part — with other domains, including nemawashi.com, ns500693.ns500693.ns500693.ns500734.ns500699.ns500693.ns500699.ns500588.ns500588.ns500699.ns500699.ns500588.ns500588.ns500602.ns500578.ns500110.dtrkdll.com, bhgre-journey.com and two others.

These mail servers are frequently paired with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.

Host names with two IP numbers:

aspmx.l.google.com resolves to two addresses: 192.178.155.26 and 2607:f8b0:4004:c17::1a.

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1b.