`nanocorp.app`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::ac43:988b^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3034::6815:c92^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.12.146^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.152.139^{🇺🇸 Cloudflare172.67.144.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`piers.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c10^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`piers.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c310^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`piers.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2310^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`piers.ns.cloudflare.com`
		A	108.162.195.16^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`piers.ns.cloudflare.com`
		A	162.159.44.16^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`piers.ns.cloudflare.com`
		A	172.64.35.16^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`piers.ns.cloudflare.com`
NS	`serenity.ns.cloudflare.com`
		A	2606:4700:50::a29f:266c^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`serenity.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c26c^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`serenity.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:226c^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`serenity.ns.cloudflare.com`
		A	108.162.194.108^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`serenity.ns.cloudflare.com`
		A	162.159.38.108^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`serenity.ns.cloudflare.com`
		A	172.64.34.108^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`serenity.ns.cloudflare.com`
MX	`inbound-smtp.us-east-1.amazonaws.com` ⭐
		A	3.211.210.226^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-211-210-226.compute-1.amazonaws.com`
		A	44.206.9.87^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-206-9-87.compute-1.amazonaws.com`
		A	44.210.166.32^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-210-166-32.compute-1.amazonaws.com`
		A	54.164.173.191^{🇺🇸 Amazon54.164.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-164-173-191.compute-1.amazonaws.com`
		A	54.197.5.236^{🇺🇸 Amazon54.196.0.0/15 EC2 IAD 54.196.0.0/15}
			PTR	`ec2-54-197-5-236.compute-1.amazonaws.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.12.146, 172.67.152.139
		IPv6 hints	2606:4700:3030::ac43:988b, 2606:4700:3034::6815:c92
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=185, name=cloudflare-ech.com
SOA	`piers.ns.cloudflare.com`dns@cloudflare.com serial=2407925937

`app`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns-tld1.charlestonroadregistry.com` ⭐
	NS	`ns-tld2.charlestonroadregistry.com`
	NS	`ns-tld3.charlestonroadregistry.com`
	NS	`ns-tld4.charlestonroadregistry.com`
	NS	`ns-tld5.charlestonroadregistry.com`
	SOA	`ns-tld1.charlestonroadregistry.com`cloud-dns-hostmaster@google.com serial=101427

🔒 HSTS Preload (+subdomains)

Same first word

nanocorp.app

nanocorp.io

nanocorp.info

nanocorp.so

nanocorp.nl

nanocorp.com

nanocorp.cl

Similar names

naprocon.com

procanon.co.za

onancorp.com

canonpro.com

proconna.com

corpnano.com

onancorp.net

anoncorp.com

nanoproc.com

pronacon.net

nanocrop.com

pronacon.com

coronanp.com

DNS History

9 records (7 active, 2 former)

●NSpiers.ns.cloudflare.com2026-04-11 → 2026-08-11 · 2 obs

● 2026-04-11 08:43:42
● 2026-08-11 03:37:20

●NSserenity.ns.cloudflare.com2026-04-11 → 2026-08-11 · 2 obs

● 2026-04-11 08:43:42
● 2026-08-11 03:37:20

●MXinbound-smtp.us-east-1.amazonaws.com2026-04-11 → 2026-08-11 · 2 obs

● 2026-04-11 08:43:42
● 2026-08-11 03:37:20

●A104.21.12.1462026-05-26 → 2026-08-11 · 2 obs

● 2026-05-26 08:46:32
● 2026-08-11 03:37:20

●A172.67.152.1392026-05-26 → 2026-08-11 · 2 obs

● 2026-05-26 08:46:32
● 2026-08-11 03:37:20

●A2606:4700:3030::ac43:988b2026-07-04 → 2026-08-11 · 3 obs

○ 2026-06-01 08:02:18
● 2026-07-04 11:33:48
● 2026-08-11 03:37:20

●A2606:4700:3034::6815:c922026-07-04 → 2026-08-11 · 3 obs

○ 2026-06-01 08:02:18
● 2026-07-04 11:33:48
● 2026-08-11 03:37:20

○A2606:4700:3034::ac43:988b2026-05-26 → 2026-06-01 · 4 obs

● 2026-05-26 08:46:32
● 2026-06-01 08:02:18
○ 2026-07-04 11:33:48
○ 2026-08-11 03:37:20

○A2606:4700:3035::6815:c922026-05-26 → 2026-06-01 · 4 obs

● 2026-05-26 08:46:32
● 2026-06-01 08:02:18
○ 2026-07-04 11:33:48
○ 2026-08-11 03:37:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
app	ns-tld2.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com...	-
nanocorp.app	serenity.ns.cloudflare.com, piers.ns.cloudflare.com	-

✅ Authoritative Response

Server:162.159.44.16

NS records: serenity.ns.cloudflare.com, piers.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for nanocorp.app (unsigned zone)

⏱️ Timing

Total: 1843ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.12.146, 172.67.152.139`
AAAA	2	`2606:4700:3030::ac43:988b, 2606:4700:3034::6815:c92`
NS	2	`piers.ns.cloudflare.com, serenity.ns.cloudflare.com`
MX	1	`inbound-smtp.us-east-1.amazonaws.com (pr`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`piers.ns.cloudflare.com dns.cloudflare.c`

Analysis

IP Addresses

nanocorp.app points to the four IP addresses 104.21.12.146, 172.67.152.139, 2606:4700:3030::ac43:988b and 2606:4700:3034::6815:c92.

Among the host names that share IP numbers with nanocorp.app are purworejo.geschool.net, impact-planning.com, naiala.com and two others.

Name Servers

nanocorp.app is served by two delegated name servers, piers.ns.cloudflare.com and serenity.ns.cloudflare.com.

nanocorp.app has the same name server delegation as a number of other domains, such as parchcraftaustralia.com, galaktyczny.pl, live-footballzone.com and two more.

The name servers of nanocorp.app overlap at least partially with those of other domains — among them duo04ren.life, intersofttest.com, algoblocks.com and two more.

The name servers sureena.ns.cloudflare.com, evelyn.ns.cloudflare.com and raphaela.ns.cloudflare.com are commonly seen alongside these name servers.

Host names resolving to 6 IP numbers:

piers.ns.cloudflare.com carries IP addresses 108.162.195.16, 162.159.44.16 and 172.64.35.16, with 3 other addresses beyond those.

serenity.ns.cloudflare.com carries IP addresses 108.162.194.108, 162.159.38.108 and 172.64.34.108, with 3 other addresses beyond those.

Mail Servers

nanocorp.app routes its mail through a single mail server, inbound-smtp.us-east-1.amazonaws.com.

nanocorp.app has the same mail server arrangement as a number of other domains, for example banuba.slack.com, rinjaninationalpark.id, normangraziani.ca and two more.

nanocorp.app shares at least some of its mail servers with other domains — for example nnlifejp.atlassian.net, mckanalyticsplatform.atlassian.net, support3ci.atlassian.net and two more.

It is common to find these mail servers paired with the mail servers inbound-smtp.us-west-2.amazonaws.com.

inbound-smtp.us-east-1.amazonaws.com directs to five IP numbers: 3.211.210.226, 44.206.9.87, 44.210.166.32 and two others.

nanocorp.app - robtex.com

nanocorp.app

app

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`nanocorp.app`

`app`