flightapi.binginternal.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`flightapi.binginternal.com`

DNSSEC	⚠️ Not signed
A	131.253.15.15^{🇺🇸 Microsoft131.253.12.0/22 MICROSOFT}
		PTR	`flightapi.binginternal.com`

`binginternal.com`

	DNSSEC	⚠️ Not signed
	A	204.79.197.200^{🇺🇸 AS8068204.79.197.0/24 Microsoft}
	NS	`dns1.p04.nsone.net` ⭐
	NS	`dns2.p04.nsone.net`
	NS	`dns3.p04.nsone.net`
	NS	`dns4.p04.nsone.net`
	NS	`ns1-204.azure-dns.com`
	NS	`ns2-204.azure-dns.net`
	NS	`ns3-204.azure-dns.org`
	NS	`ns4-204.azure-dns.info`
	SOA	`dns1.p04.nsone.net`hostmaster@nsone.net serial=1654551304

PTR for

15.15.253.131.in-addr.arpa

Same first word

flightapi.io

DNS History

1 record (1 active, 0 former)

●A131.253.15.152026-03-05 → 2026-08-16 · 2 obs

● 2026-03-05 11:35:56
● 2026-08-16 03:29:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
binginternal.com	dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net...	2 records

✅ Authoritative Response

Server:13.107.236.204

NS records: dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net, ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns4-204.azure-dns.info, ns3-204.azure-dns.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for binginternal.com (unsigned zone)

⏱️ Timing

Total: 363ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`131.253.15.15`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-204.azure-dns.com, ns1-204.azure-dns.com)

Analysis

IP Addresses

flightapi.binginternal.com resolves to just one IP address, 131.253.15.15.