🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`binarypanda.com`

DNSSEC	⚠️ Not signed
A	162.255.139.122^{🇺🇸 AS47869162.255.136.0/22 Netrouting Miami}
		PTR	`162-255-139-122.static.hvvc.us`
NS	`ns-290.awsdns-36.com` ⭐
		A	2600:9000:5301:2200::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-290.awsdns-36.com`
		A	205.251.193.34^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-290.awsdns-36.com`
NS	`ns-1148.awsdns-15.org`
		A	2600:9000:5304:7c00::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1148.awsdns-15.org`
		A	205.251.196.124^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1148.awsdns-15.org`
NS	`ns-1757.awsdns-27.co.uk`
		A	2600:9000:5306:dd00::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1757.awsdns-27.co.uk`
		A	205.251.198.221^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1757.awsdns-27.co.uk`
NS	`ns-908.awsdns-49.net`
		A	2600:9000:5303:8c00::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-908.awsdns-49.net`
		A	205.251.195.140^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-908.awsdns-49.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	64.233.180.26^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽²⁰⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-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.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`aspmx2.googlemail.com`⁽⁴⁰⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`aspmx3.googlemail.com`⁽⁵⁰⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
SOA	`ns-290.awsdns-36.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=1787813540

Same first word

binarypanda.com

Previous names

Next names

DNS History

11 records (10 active, 1 former)

●NSns-1148.awsdns-15.org2015-08-20 → 2026-08-27 · 2 obs

● 2015-08-20 09:21:50
● 2026-08-27 07:13:52

●NSns-1757.awsdns-27.co.uk2015-08-20 → 2026-08-27 · 2 obs

● 2015-08-20 09:21:50
● 2026-08-27 07:13:52

●NSns-290.awsdns-36.com2015-08-20 → 2026-08-27 · 2 obs

● 2015-08-20 09:21:50
● 2026-08-27 07:13:52

●NSns-908.awsdns-49.net2015-08-20 → 2026-08-27 · 2 obs

● 2015-08-20 09:21:50
● 2026-08-27 07:13:52

●MXalt1.aspmx.l.google.com2015-08-20 → 2026-08-27 · 2 obs

● 2015-08-20 09:21:50
● 2026-08-27 07:13:52

●MXalt2.aspmx.l.google.com2015-08-20 → 2026-08-27 · 2 obs

● 2015-08-20 09:21:50
● 2026-08-27 07:13:52

●MXaspmx.l.google.com2015-08-20 → 2026-08-27 · 2 obs

● 2015-08-20 09:21:50
● 2026-08-27 07:13:52

●MXaspmx2.googlemail.com2015-08-20 → 2026-08-27 · 2 obs

● 2015-08-20 09:21:50
● 2026-08-27 07:13:52

●MXaspmx3.googlemail.com2015-08-20 → 2026-08-27 · 2 obs

● 2015-08-20 09:21:50
● 2026-08-27 07:13:52

●A162.255.139.1222026-08-20 → 2026-08-27 · 3 obs

○ 2017-04-18 11:49:08
● 2026-08-20 12:13:04
● 2026-08-27 07:13:52

○A205.237.197.1192015-08-20 → 2017-04-18 · 4 obs

● 2015-08-20 09:21:50
● 2017-04-18 11:49:08
○ 2026-08-20 12:13:04
○ 2026-08-27 07:13:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, e.gtld-servers.net, l.gtld-servers.net, k.gtld-servers.net...	-
binarypanda.com	ns-290.awsdns-36.com, ns-908.awsdns-49.net, ns-1757.awsdns-27.co.uk, ns-1148.awsdns-15.org	2 records

✅ Authoritative Response

Server:205.251.193.34

NS records: ns-290.awsdns-36.com, ns-908.awsdns-49.net, ns-1757.awsdns-27.co.uk, ns-1148.awsdns-15.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for binarypanda.com (unsigned zone)

⏱️ Timing

Total: 566ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`162.255.139.122`
NS	4	`ns-1148.awsdns-15.org, ns-1757.awsdns-27.co.uk...`
MX	5	`aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 20)...`
SOA	1	`ns-290.awsdns-36.com awsdns-hostmaster.a`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-290.awsdns-36.com, ns-290.awsdns-36.com)

Analysis

IP Addresses

binarypanda.com resolves to just one IP address, 162.255.139.122.

binarypanda.com shares its IP numbers with other host names like supergoodbeer.com, 162-255-139-122.static.hvvc.us and supergoodburgers.com.

Name Servers

The NS records for binarypanda.com point to four name servers: ns-290.awsdns-36.com, ns-908.awsdns-49.net, ns-1148.awsdns-15.org and ns-1757.awsdns-27.co.uk.

binarypanda.com partially shares its NS delegation with several other domains, including jetgw.com, climbing-bluebird.com, paradoxsecure.com and two others.

ns-290.awsdns-36.com, ns-908.awsdns-49.net, ns-1148.awsdns-15.org and ns-1757.awsdns-27.co.uk each carry two IP addresses. ns-290.awsdns-36.com has 205.251.193.34 and 2600:9000:5301:2200::1; ns-908.awsdns-49.net has 205.251.195.140 and 2600:9000:5303:8c00::1; ns-1148.awsdns-15.org has 205.251.196.124 and 2600:9000:5304:7c00::1; ns-1757.awsdns-27.co.uk has 205.251.198.221 and 2600:9000:5306:dd00::1.

Mail Servers

Mail for binarypanda.com is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

There is at least a partial MX overlap between binarypanda.com and other domains, including awretailmexico.com, angga.net, civicsciencemedia.com and two others.

These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt4.aspmx.l.google.com and 3 others.

Host names that have two IP addresses:

aspmx2.googlemail.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.

aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.

aspmx.l.google.com directs traffic to 64.233.180.26 and 2607:f8b0:4004:c23::1b.

alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.

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

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c14::1a IP addresses each.

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 192.178.234.26 IP addresses each.

Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.27 IP addresses each.