yespper.com - dns.ninja

`yespper.com`

DNSSEC	⚠️ Not signed
A	24.199.90.248^{🇺🇸 DIGITALOCEAN24.199.80.0/20 DigitalOcean}
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:c1b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f27.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.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.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
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`
SOA	`ns1.digitalocean.com`hostmaster@yespper.com serial=0

`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=1786047794

Same first word

yespper.com

Similar names

peresyp.ru

peresyp.ua

yesprep.org

yesprep.com

peresyp.zp.ua

peerspy.com

DNS History

10 records (10 active, 0 former)

●NSns1.digitalocean.com2018-06-16 → 2026-08-06 · 2 obs

● 2018-06-16 23:00:30
● 2026-08-06 20:37:54

●NSns2.digitalocean.com2018-06-16 → 2026-08-06 · 2 obs

● 2018-06-16 23:00:30
● 2026-08-06 20:37:54

●NSns3.digitalocean.com2018-06-16 → 2026-08-06 · 2 obs

● 2018-06-16 23:00:30
● 2026-08-06 20:37:54

●MXalt1.aspmx.l.google.com2026-02-26 → 2026-08-06 · 2 obs

● 2026-02-26 23:40:06
● 2026-08-06 20:37:54

●MXalt2.aspmx.l.google.com2026-02-26 → 2026-08-06 · 2 obs

● 2026-02-26 23:40:06
● 2026-08-06 20:37:54

●MXalt3.aspmx.l.google.com2026-02-26 → 2026-08-06 · 2 obs

● 2026-02-26 23:40:06
● 2026-08-06 20:37:54

●MXalt4.aspmx.l.google.com2026-02-26 → 2026-08-06 · 2 obs

● 2026-02-26 23:40:06
● 2026-08-06 20:37:54

●MXaspmx.l.google.com2026-02-26 → 2026-08-06 · 2 obs

● 2026-02-26 23:40:06
● 2026-08-06 20:37:54

●MXinbound-smtp.us-east-1.amazonaws.com2026-02-26 → 2026-08-06 · 2 obs

● 2026-02-26 23:40:06
● 2026-08-06 20:37:54

●A24.199.90.2482026-02-26 → 2026-08-06 · 2 obs

● 2026-02-26 23:40:06
● 2026-08-06 20:37:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, d.gtld-servers.net, c.gtld-servers.net, j.gtld-servers.net...	-
yespper.com	ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com	3 records

✅ Authoritative Response

Server:172.64.52.210

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for yespper.com (unsigned zone)

⏱️ Timing

Total: 220ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`24.199.90.248`
NS	3	`ns3.digitalocean.com, ns1.digitalocean.com...`
MX	6	`alt2.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)...`
SOA	1	`ns1.digitalocean.com hostmaster.yespper.`

📌 Glue Records Collected

Total: 3

Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)

Analysis

IP Addresses

yespper.com resolves to one IP address: 24.199.90.248.

Name Servers

yespper.com carries NS records delegating to ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.

There is at least partial name server overlap between yespper.com and other domains — twowings.com, damagemonitor.com, hightoweragency.com and two more among them.

These name servers are routinely deployed together with the name servers ns4.digitalocean.com.

ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com are three hostnames that each resolve to a pair of IP addresses: ns1.digitalocean.com to 172.64.52.210 and 2606:4700:52::ac40:34d2, ns2.digitalocean.com to 172.64.53.21 and 2606:4700:5a::ac40:3515, and ns3.digitalocean.com to 172.64.49.209 and 2606:4700:52::ac40:31d1.

Mail Servers

yespper.com accepts email via 6 mail servers: inbound-smtp.us-east-1.amazonaws.com, aspmx.l.google.com, alt1.aspmx.l.google.com and 3 other.

yespper.com has at least partial mail server overlap with other domains such as ns500693.ns500734.ns500693.ns500693.ns500699.ns500693.ns500699.ns500588.ns500699.ns500632.ns500683.ns500632.ns500632.ns500612.dtrkdll.com, ns500731.ns500731.ns500671.ns500688.ns500704.ns500688.ns500705.ns500704.ns500688.ns500649.ns500649.lustychickser.com, ns500698.ns500758.ns500759.ns500759.ns500735.ns500736.ns500735.ns500735.ns500698.ns500708.ns500576.ns500619.ns500652.ns500619.trackreceptor.com and two more.

These mail servers commonly co-occur with mail servers alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and 4 others.

Hostnames pointing to five IP numbers:

inbound-smtp.us-east-1.amazonaws.com resolves to four IP addresses: 3.211.210.226, 44.206.9.87, 44.210.166.32 and two others.

Hostnames that resolve to two IP addresses:

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

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

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

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

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