specific.app - dns.ninja

`specific.app`

DNSSEC	⚠️ Not signed
A	94.237.83.139^{🇫🇮 UPCLOUD94.237.80.0/20 -DE-FRA1-NET}
		PTR	`94-237-83-139.de-fra1.upcloud.host`
NS	`ns1.digitalocean.com` ⭐
		A	2606:4700:52::ac40:34d2^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
		A	172.64.52.210^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
NS	`ns2.digitalocean.com`
		A	2606:4700:5a::ac40:3515^{🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
		A	172.64.53.21^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
NS	`ns3.digitalocean.com`
		A	2606:4700:52::ac40:31d1^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
		A	172.64.49.209^{🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1f::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f27.1e100.net`
		A	64.233.180.27^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.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	`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.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.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.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=MsyQFECCJN1K5B2Bi-NVCgkTQcyaQEIEB8Sb80h3uss`
TXT	`v=spf1 include:_spf.google.com include:mailgun.org include:sendgrid.net ~all`
SOA	`ns1.digitalocean.com`hostmaster@specific.app serial=0

`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

specific.info

specific.no

specific.com

specific.dk

specific.diet

specific.it

specific.net

specific.co.nz

specific.technology

specific.is

specific.eu

specific.nu

specific.nl

specific.ch

specific.jp

specific.cz

specific.org.nz

specific.ro

specific.fm

specific.me

specific.dev

specific.app

specific.co.jp

specific.ee

specific.cn

specific.ir

specific.co.za

specific.be

specific.at

specific.pl

specific.se

specific.mobi

specific.co

specific.de

specific.tc

DNS History

9 records (9 active, 0 former)

●NSns1.digitalocean.com2026-03-19 → 2026-08-04 · 2 obs

● 2026-03-19 23:34:50
● 2026-08-04 02:21:24

●NSns2.digitalocean.com2026-03-19 → 2026-08-04 · 2 obs

● 2026-03-19 23:34:50
● 2026-08-04 02:21:24

●NSns3.digitalocean.com2026-03-19 → 2026-08-04 · 2 obs

● 2026-03-19 23:34:50
● 2026-08-04 02:21:24

●MXalt1.aspmx.l.google.com2026-03-19 → 2026-08-04 · 2 obs

● 2026-03-19 23:34:50
● 2026-08-04 02:21:24

●MXalt2.aspmx.l.google.com2026-03-19 → 2026-08-04 · 2 obs

● 2026-03-19 23:34:50
● 2026-08-04 02:21:24

●MXalt3.aspmx.l.google.com2026-03-19 → 2026-08-04 · 2 obs

● 2026-03-19 23:34:50
● 2026-08-04 02:21:24

●MXalt4.aspmx.l.google.com2026-03-19 → 2026-08-04 · 2 obs

● 2026-03-19 23:34:50
● 2026-08-04 02:21:24

●MXaspmx.l.google.com2026-03-19 → 2026-08-04 · 2 obs

● 2026-03-19 23:34:50
● 2026-08-04 02:21:24

●A94.237.83.1392026-03-19 → 2026-08-04 · 2 obs

● 2026-03-19 23:34:50
● 2026-08-04 02:21:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
app	ns-tld1.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...	-
specific.app	ns1.digitalocean.com, ns3.digitalocean.com, ns2.digitalocean.com	-

✅ Authoritative Response

Server:172.64.53.21

NS records: ns1.digitalocean.com, ns3.digitalocean.com, ns2.digitalocean.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for specific.app (unsigned zone)

⏱️ Timing

Total: 349ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`94.237.83.139`
NS	3	`ns1.digitalocean.com, ns2.digitalocean.com...`
MX	5	`alt1.aspmx.l.google.com (pri: 5), alt4.aspmx.l.google.com (pri: 10)...`
TXT	2	`v=spf1 include:_spf.google.com include:m, google-site-verification=MsyQFECCJN1K5B2`
SOA	1	`ns1.digitalocean.com hostmaster.specific`

Analysis

IP Addresses

specific.app resolves to one IP address: 94.237.83.139.

lb-0a9b8e4ad1994142b314afce7e5415ef-1.upcloudlb.com, smarkup.com, sursec.co.uk and two other host names share IP numbers with specific.app.

Name Servers

specific.app is delegated to three name servers: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.

specific.app partially shares its NS delegation with several other domains, including trachenko.com, mr-blue.in, ishookdaily.com and two others.

ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com each resolve to two IP addresses: ns1.digitalocean.com resolves to 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com resolves to 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com resolves to 172.64.49.209 and 2606:4700:52::ac40:31d1.

Mail Servers

Mail for specific.app is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

specific.app has at least partial mail server overlap with other domains such as ns500758.ns500698.ns500758.ns500698.ns500736.ns500698.ns500698.ns500735.ns500735.ns500698.ns500698.ns500619.ns500576.ns500652.ns500619.ns500619.trackreceptor.com, ns500758.ns500758.ns500758.ns500758.ns500735.ns500735.ns500735.ns500736.ns500735.ns500736.ns500708.ns500698.ns500708.ns500708.ns500652.trackreceptor.com, vistol.com and two more.

These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Hostnames that resolve to two IP addresses:

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

alt1.aspmx.l.google.com points to 108.177.123.27 and 2800:3f0:4003:c0f::1a.

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

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

alt4.aspmx.l.google.com points to 172.253.157.27 and 2a00:1450:400c:c23::1b.