🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`batchbound.com`

DNSSEC	⚠️ Not signed
A	2600:1f18:16e:df01::258^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
A	2600:1f18:16e:df01::259^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
A	18.208.88.157^{🇺🇸 Amazon18.208.0.0/13 EC2 IAD prefix}
A	98.84.224.111^{🇺🇸 Amazon98.80.0.0/13 EC2 IAD Prefix}
NS	`dns1.p01.nsone.net` ⭐
		A	2620:4d:4000:6259:7:1:0:1^{🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1}
			PTR	`dns1.p01.nsone.net`
		A	198.51.44.1^{🇺🇸 NSONE198.51.44.0/24}
			PTR	`dns1.p01.nsone.net`
NS	`dns1.p02.nsone.net`
		A	2620:4d:4000:6259:7:2:0:1^{🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1}
			PTR	`dns1.p02.nsone.net`
		A	198.51.44.2^{🇺🇸 NSONE198.51.44.0/24}
			PTR	`dns1.p02.nsone.net`
NS	`dns2.p02.nsone.net`
		A	2a00:edc0:6259:7:2::2^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns2.p02.nsone.net`
		A	198.51.45.2^{🇺🇸 NSONE198.51.45.0/24}
			PTR	`dns2.p02.nsone.net`
NS	`dns3.p02.nsone.net`
		A	2620:4d:4000:6259:7:2:0:3^{🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1}
			PTR	`dns3.p02.nsone.net`
		A	198.51.44.66^{🇺🇸 NSONE198.51.44.0/24}
			PTR	`dns3.p02.nsone.net`
NS	`dns4.p02.nsone.net`
		A	2a00:edc0:6259:7:2::4^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns4.p02.nsone.net`
		A	198.51.45.66^{🇺🇸 NSONE198.51.45.0/24}
			PTR	`dns4.p02.nsone.net`
MX	`mx1.improvmx.com` ⭐
		A	2a05:d012:412:e201:88aa:e7b9:7a43:12d7^{🇫🇷 Amazon2a05:d012:400::/38 AMAZON AWS}
		A	2a05:d012:412:e202:f36:2c1f:1a49:d38a^{🇫🇷 Amazon2a05:d012:400::/38 AMAZON AWS}
		A	2a05:d012:412:e203:373a:f51a:4a85:1d25^{🇫🇷 Amazon2a05:d012:400::/38 AMAZON AWS}
		A	13.37.195.136^{🇫🇷 Amazon13.36.0.0/14 EC2 CDG Prefix}
			PTR	`ec2-13-37-195-136.eu-west-3.compute.amazonaws.com`
		A	15.236.236.160^{🇫🇷 Amazon15.236.0.0/15 EC2 CDG prefix}
			PTR	`ec2-15-236-236-160.eu-west-3.compute.amazonaws.com`
		A	35.181.18.45^{🇫🇷 Amazon35.181.0.0/16 EC2 CDG prefix}
			PTR	`ec2-35-181-18-45.eu-west-3.compute.amazonaws.com`
MX	`mx2.improvmx.com`⁽²⁰⁾
		A	2a05:d012:412:e201:1f6e:f6e4:8fd7:4678^{🇫🇷 Amazon2a05:d012:400::/38 AMAZON AWS}
		A	2a05:d012:412:e202:e81e:cc44:3b53:8a3d^{🇫🇷 Amazon2a05:d012:400::/38 AMAZON AWS}
		A	2a05:d012:412:e203:7e33:3d9c:28d7:ee20^{🇫🇷 Amazon2a05:d012:400::/38 AMAZON AWS}
		A	13.36.107.63^{🇫🇷 Amazon13.36.0.0/14 EC2 CDG Prefix}
			PTR	`ec2-13-36-107-63.eu-west-3.compute.amazonaws.com`
		A	13.36.222.39^{🇫🇷 Amazon13.36.0.0/14 EC2 CDG Prefix}
			PTR	`ec2-13-36-222-39.eu-west-3.compute.amazonaws.com`
		A	15.236.61.92^{🇫🇷 Amazon15.236.0.0/15 EC2 CDG prefix}
			PTR	`ec2-15-236-61-92.eu-west-3.compute.amazonaws.com`
TXT	`firebase=batchbound-prod`
TXT	`v=spf1 include:_spf.firebasemail.com ~all`
TXT	`brevo-code:4615c378b6af9c879a61e90e0c074900`
TXT	`google-site-verification=PJwF0chlrHZFgf9iD9twYMyc5P_KXjfBol3wq64cWeM`
SOA	`dns1.p01.nsone.net`domains+netlify@netlify.com serial=1781884573

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

Same first word

batchbound.com

Previous names

Next names

DNS History

15 records (11 active, 4 former)

●NSdns1.p01.nsone.net2026-08-28 → 2026-09-02 · 2 obs

● 2026-08-28 16:15:02
● 2026-09-02 05:19:34

●NSdns1.p02.nsone.net2026-08-28 → 2026-09-02 · 2 obs

● 2026-08-28 16:15:02
● 2026-09-02 05:19:34

●NSdns2.p02.nsone.net2026-08-28 → 2026-09-02 · 2 obs

● 2026-08-28 16:15:02
● 2026-09-02 05:19:34

●NSdns3.p02.nsone.net2026-08-28 → 2026-09-02 · 2 obs

● 2026-08-28 16:15:02
● 2026-09-02 05:19:34

●NSdns4.p02.nsone.net2026-08-28 → 2026-09-02 · 2 obs

● 2026-08-28 16:15:02
● 2026-09-02 05:19:34

●MXmx1.improvmx.com2026-08-28 → 2026-09-02 · 2 obs

● 2026-08-28 16:15:02
● 2026-09-02 05:19:34

●MXmx2.improvmx.com2026-08-28 → 2026-09-02 · 2 obs

● 2026-08-28 16:15:02
● 2026-09-02 05:19:34

●A18.208.88.1572026-08-31 → 2026-09-02 · 3 obs

○ 2026-08-28 16:15:02
● 2026-08-31 22:52:08
● 2026-09-02 05:19:34

●A2600:1f18:16e:df01::2582026-08-31 → 2026-09-02 · 3 obs

○ 2026-08-28 16:15:02
● 2026-08-31 22:52:08
● 2026-09-02 05:19:34

●A2600:1f18:16e:df01::2592026-08-31 → 2026-09-02 · 3 obs

○ 2026-08-28 16:15:02
● 2026-08-31 22:52:08
● 2026-09-02 05:19:34

○A2a05:d014:58f:6200::2582026-08-28 → 2026-08-28 · 3 obs

● 2026-08-28 16:15:02
○ 2026-08-31 22:52:08
○ 2026-09-02 05:19:34

○A2a05:d014:58f:6200::2592026-08-28 → 2026-08-28 · 3 obs

● 2026-08-28 16:15:02
○ 2026-08-31 22:52:08
○ 2026-09-02 05:19:34

○A35.157.26.1352026-08-28 → 2026-08-28 · 3 obs

● 2026-08-28 16:15:02
○ 2026-08-31 22:52:08
○ 2026-09-02 05:19:34

○A63.176.8.2182026-08-28 → 2026-08-28 · 3 obs

● 2026-08-28 16:15:02
○ 2026-08-31 22:52:08
○ 2026-09-02 05:19:34

●A98.84.224.1112026-08-31 → 2026-09-02 · 3 obs

○ 2026-08-28 16:15:02
● 2026-08-31 22:52:08
● 2026-09-02 05:19:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
batchbound.com	dns1.p02.nsone.net, dns2.p02.nsone.net, dns3.p02.nsone.net, dns4.p02.nsone.net	-

✅ Authoritative Response

Server:198.51.45.66

NS records: dns1.p02.nsone.net, dns2.p02.nsone.net, dns3.p02.nsone.net, dns4.p02.nsone.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for batchbound.com (unsigned zone)

⏱️ Timing

Total: 709ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`98.84.224.111, 18.208.88.157`
AAAA	2	`2600:1f18:16e:df01::259, 2600:1f18:16e:df01::258`
NS	4	`dns1.p02.nsone.net, dns2.p02.nsone.net...`
MX	2	`mx2.improvmx.com (pri: 20), mx1.improvmx.com (pri: 10)`
TXT	4	`firebase=batchbound-prod, v=spf1 include:_spf.firebasemail.com ~al...`
SOA	1	`dns1.p01.nsone.net domains+netlify.netli`

Analysis

IP Addresses

batchbound.com resolves to four IP addresses: 18.208.88.157, 98.84.224.111, 2600:1f18:16e:df01::258 and 2600:1f18:16e:df01::259.

Among the host names that share IP numbers with batchbound.com are vtcodecamp.org, wallet-fixers.netlify.app, oaradar.com and two others.

Name Servers

The authoritative name servers for batchbound.com are dns1.p01.nsone.net, dns1.p02.nsone.net, dns2.p02.nsone.net and two others.

batchbound.com shares at least some of its name servers with other domains, including stevenhaulenbeek.com, blickpunkte-design.de, mv-ertl.at and two others.

These name servers are frequently seen alongside dns3.p02.nsone.net, dns4.p02.nsone.net, ns01.squarespacedns.com and 7 other name servers.

Hosts with two IP numbers each:

dns1.p01.nsone.net resolves to two addresses: 198.51.44.1 and 2620:4d:4000:6259:7:1:0:1.

dns1.p02.nsone.net resolves to two addresses: 198.51.44.2 and 2620:4d:4000:6259:7:2:0:1.

dns2.p02.nsone.net resolves to two addresses: 198.51.45.2 and 2a00:edc0:6259:7:2::2.

dns3.p02.nsone.net resolves to two addresses: 198.51.44.66 and 2620:4d:4000:6259:7:2:0:3.

dns4.p02.nsone.net resolves to two addresses: 198.51.45.66 and 2a00:edc0:6259:7:2::4.

Mail Servers

The MX records for batchbound.com point to two mail servers: mx1.improvmx.com and mx2.improvmx.com.

batchbound.com has the same mail server arrangement as a number of other domains, for example kurmannpartners.com, drlozanolominchar.com, taxi1234.com and two more.

batchbound.com shares at least some of its mail servers with other domains — for example measly-bellbottom.de, howles.com, hubdevice.com and two more.

Host names resolving to 6 IP numbers:

mx1.improvmx.com resolves to 13.37.195.136, 15.236.236.160 and 35.181.18.45 among others, with 3 other IP addresses in total.

mx2.improvmx.com resolves to 13.36.107.63, 13.36.222.39 and 15.236.61.92 among others, with 3 other IP addresses in total.

batchbound.com - robtex.com

batchbound.com

com

Same first word

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`batchbound.com`

`com`