yapperbot.com - dns.ninja

`yapperbot.com`

DNSSEC	⚠️ Not signed
A	54.157.53.158^{🇺🇸 Amazon54.156.0.0/14 EC2 IAD prefix}
		PTR	`ec2-54-157-53-158.compute-1.amazonaws.com`
NS	`ns-356.awsdns-44.com` ⭐
		A	2600:9000:5301:6400::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-356.awsdns-44.com`
		A	205.251.193.100^{🇺🇸 Amazon205.251.193.0/24 prefix}
NS	`ns-1430.awsdns-50.org`
		A	2600:9000:5305:9600::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1430.awsdns-50.org`
		A	205.251.197.150^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1430.awsdns-50.org`
NS	`ns-1762.awsdns-28.co.uk`
		A	2600:9000:5306:e200::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1762.awsdns-28.co.uk`
		A	205.251.198.226^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1762.awsdns-28.co.uk`
NS	`ns-531.awsdns-02.net`
		A	2600:9000:5302:1300::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-531.awsdns-02.net`
		A	205.251.194.19^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-531.awsdns-02.net`
MX	`yapperbot-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::14^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-byapr04cu00204.inbound.protection.outlook.com`
		A	2a01:111:f403:c91d::a^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-co1pr21cu00202.inbound.protection.outlook.com`
		A	2a01:111:f403:f902::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl2pr04cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:f90d::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sn1pr0501cu00200.inbound.protection.outlook.com`
		A	52.101.9.2^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mn2pr02cu00202.inbound.protection.outlook.com`
		A	52.101.10.10^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn8pr05cu00102.inbound.protection.outlook.com`
		A	52.101.40.1^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
		A	52.101.42.14^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mw2pr04cu00106.inbound.protection.outlook.com`
TXT	`google-site-verification=f2kHeypbZwgNYzYPUa15bBhpjH0f9mQqh_AaYHzTNY4`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns-356.awsdns-44.com`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=1782574810

Same first word

yapperbot.com

Similar names

betyappro.com

betoryapp.com

DNS History

11 records (6 active, 5 former)

●NSns-1430.awsdns-50.org2026-03-30 → 2026-06-27 · 3 obs

○ 2017-09-07 20:10:38
● 2026-03-30 02:26:10
● 2026-06-27 16:03:34

●NSns-1762.awsdns-28.co.uk2026-03-30 → 2026-06-27 · 3 obs

○ 2017-09-07 20:10:38
● 2026-03-30 02:26:10
● 2026-06-27 16:03:34

●NSns-356.awsdns-44.com2026-03-30 → 2026-06-27 · 3 obs

○ 2017-09-07 20:10:38
● 2026-03-30 02:26:10
● 2026-06-27 16:03:34

●NSns-531.awsdns-02.net2026-03-30 → 2026-06-27 · 3 obs

○ 2017-09-07 20:10:38
● 2026-03-30 02:26:10
● 2026-06-27 16:03:34

○NSns1.yapperbot.com2017-09-07 → 2017-09-07 · 3 obs

● 2017-09-07 20:10:38
○ 2026-03-30 02:26:10
○ 2026-06-27 16:03:34

○NSns2.yapperbot.com2017-09-07 → 2017-09-07 · 3 obs

● 2017-09-07 20:10:38
○ 2026-03-30 02:26:10
○ 2026-06-27 16:03:34

○MXfw1a.yapperbot.com2017-09-07 → 2017-09-07 · 3 obs

● 2017-09-07 20:10:38
○ 2026-03-30 02:26:10
○ 2026-06-27 16:03:34

○MXfw2a.yapperbot.com2017-09-07 → 2017-09-07 · 3 obs

● 2017-09-07 20:10:38
○ 2026-03-30 02:26:10
○ 2026-06-27 16:03:34

●MXyapperbot-com.mail.protection.outlook.com2026-03-30 → 2026-06-27 · 3 obs

○ 2017-09-07 20:10:38
● 2026-03-30 02:26:10
● 2026-06-27 16:03:34

○A41.185.65.152017-09-07 → 2017-09-07 · 3 obs

● 2017-09-07 20:10:38
○ 2026-03-30 02:26:10
○ 2026-06-27 16:03:34

●A54.157.53.1582026-03-30 → 2026-06-27 · 3 obs

○ 2017-09-07 20:10:38
● 2026-03-30 02:26:10
● 2026-06-27 16:03:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, b.gtld-servers.net, h.gtld-servers.net, f.gtld-servers.net...	-
yapperbot.com	ns-531.awsdns-02.net, ns-356.awsdns-44.com, ns-1762.awsdns-28.co.uk, ns-1430.awsdns-50.org	2 records

✅ Authoritative Response

Server:205.251.194.19

NS records: ns-531.awsdns-02.net, ns-356.awsdns-44.com, ns-1762.awsdns-28.co.uk, ns-1430.awsdns-50.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for yapperbot.com (unsigned zone)

⏱️ Timing

Total: 462ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.157.53.158`
NS	4	`ns-1430.awsdns-50.org, ns-1762.awsdns-28.co.uk...`
MX	1	`yapperbot-com.mail.protection.outlook.co`
TXT	2	`google-site-verification=f2kHeypbZwgNYzY, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns-356.awsdns-44.com awsdns-hostmaster.a`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-356.awsdns-44.com, ns-356.awsdns-44.com)

Analysis

IP Addresses

yapperbot.com directs to one IP number, which is 54.157.53.158.

ec2-54-157-53-158.compute-1.amazonaws.com is an example of another host name that shares IP numbers with yapperbot.com.

Name Servers

The domain yapperbot.com is delegated to these four name servers: ns-356.awsdns-44.com, ns-531.awsdns-02.net, ns-1430.awsdns-50.org and ns-1762.awsdns-28.co.uk.

yapperbot.com partially shares its NS delegation with several other domains, including 22.193.18.in-addr.arpa, 149.70.3.in-addr.arpa, 209.93.54.in-addr.arpa and two others.

In DNS configurations, these name servers often share authority with ns1-24-eu-central-1.ec2-rdns.amazonaws.com, ns2-24-eu-central-1.ec2-rdns.amazonaws.com, ns3-24-eu-central-1.ec2-rdns.amazonaws.com and 7 other name servers.

ns-356.awsdns-44.com, ns-531.awsdns-02.net, ns-1430.awsdns-50.org and ns-1762.awsdns-28.co.uk each carry two IP addresses. ns-356.awsdns-44.com has 205.251.193.100 and 2600:9000:5301:6400::1; ns-531.awsdns-02.net has 205.251.194.19 and 2600:9000:5302:1300::1; ns-1430.awsdns-50.org has 205.251.197.150 and 2600:9000:5305:9600::1; ns-1762.awsdns-28.co.uk has 205.251.198.226 and 2600:9000:5306:e200::1.

Mail Servers

yapperbot.com routes its mail through a single mail server, yapperbot-com.mail.protection.outlook.com.

yapperbot-com.mail.protection.outlook.com directs to 8 IP numbers, including 52.101.9.2, 52.101.10.10 and 52.101.40.1, along with 5 other.