g.api.binance.com - dns.ninja

g.api.binance.com

DNSSEC⚠️ Not signed
A3.112.121.17πŸ‡―πŸ‡΅ Amazon3.112.0.0/14 EC2 NRT prefix
PTRec2-3-112-121-17.ap-northeast-1.compute.amazonaws.com
A13.113.235.103πŸ‡―πŸ‡΅ Amazon13.112.0.0/14 EC2 NRT prefix
A13.196.139.225πŸ‡ΊπŸ‡Έ Amazon13.192.0.0/13
TXTdobbmei4jnjlh.cloudfront.net

api.binance.com

CNAMEd3h36i1mno13q3.cloudfront.net
DNSSEC⚠️ Not signed
A13.226.219.154πŸ‡ΊπŸ‡Έ Amazon13.226.216.0/21 - Cloudfront
NSns-1407.awsdns-47.org ⭐
NSns-1565.awsdns-03.co.uk
NSns-394.awsdns-49.com
NSns-859.awsdns-43.net
HTTPSHTTP/2
SOAns-1407.awsdns-47.orgawsdns-hostmaster@amazon.com serial=1
WOT: SAFE (62/100)
WOT: SAFE (70/100)

Subdomains

Same first word

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
binance.comns-234.awsdns-29.com, ns-735.awsdns-27.net, ns-1701.awsdns-20.co.uk, ns-1319.awsdns-36.org2 records

βœ… Authoritative Response

Server:205.251.198.165

NS records: ns-234.awsdns-29.com, ns-735.awsdns-27.net, ns-1701.awsdns-20.co.uk, ns-1319.awsdns-36.org

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for binance.com (unsigned zone)

⏱️ Timing

Total: 455ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A33.112.121.17, 13.196.139.225...
TXT1dobbmei4jnjlh.cloudfront.net

πŸ“Œ Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-234.awsdns-29.com, ns-234.awsdns-29.com)

Analysis

Hierarchy

annalyn.g.api.binance.com and activate-11.g.api.binance.com are both subdomains of g.api.binance.com.

IP Addresses

g.api.binance.com resolves to three IP addresses: 3.112.121.17, 13.113.235.103 and 13.196.139.225.

autodiscover.bm.api.binance.com, 057.dev.api.binance.com, support-21.binance.com and two other host names share IP numbers with g.api.binance.com.