bf9connect.com - dns.ninja

`bf9connect.com`

DNSSEC	⚠️ Not signed
A	192.185.24.17^{🇺🇸 ORACLE-OCI-31898192.185.24.0/21 Google}
		PTR	`192-185-24-17.unifiedlayer.com`
NS	`ns313.websitewelcome.com` ⭐
		A	192.185.24.134^{🇺🇸 ORACLE-OCI-31898192.185.24.0/21 Google}
			PTR	`ns313.websitewelcome.com`
NS	`ns314.websitewelcome.com` ⚠️ Not in zone NS records
		A	192.185.24.135^{🇺🇸 ORACLE-OCI-31898192.185.24.0/21 Google}
			PTR	`ns314.websitewelcome.com`
NS	`ns314websitewelcome.com` ⚠️ Not in parent delegation
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c06::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bg-in-f26.1e100.net`
		A	142.250.31.26^{🇺🇸 Google142.250.31.0/24}
			PTR	`bj-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.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	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 a mx include:websitewelcome.com ~all`
SOA	`ns313.websitewelcome.com`jessica@insalaco.gmail.com 2026-06-21 #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=1786029509

Same first word

bf9connect.com

DNS History

17 records (9 active, 8 former)

○NSns23.domaincontrol.com2015-06-09 → 2017-02-20 · 4 obs

● 2015-06-09 10:56:08
● 2017-02-20 03:24:40
○ 2019-03-10 22:41:50
○ 2026-08-06 15:27:58

○NSns24.domaincontrol.com2015-06-09 → 2017-02-20 · 4 obs

● 2015-06-09 10:56:08
● 2017-02-20 03:24:40
○ 2019-03-10 22:41:50
○ 2026-08-06 15:27:58

●NSns313.websitewelcome.com2019-03-10 → 2026-08-06 · 3 obs

○ 2017-02-20 03:24:40
● 2019-03-10 22:41:50
● 2026-08-06 15:27:58

●NSns314.websitewelcome.com2026-03-01 → 2026-08-06 · 3 obs

○ 2019-03-10 22:41:50
● 2026-03-01 12:58:14
● 2026-08-06 15:27:58

●NSns314websitewelcome.com2019-03-10 → 2026-08-06 · 3 obs

○ 2017-02-20 03:24:40
● 2019-03-10 22:41:50
● 2026-08-06 15:27:58

●MXalt1.aspmx.l.google.com2016-04-24 → 2026-08-06 · 3 obs

○ 2016-01-29 12:13:46
● 2016-04-24 18:55:08
● 2026-08-06 15:27:58

●MXalt2.aspmx.l.google.com2016-04-24 → 2026-08-06 · 3 obs

○ 2016-01-29 12:13:46
● 2016-04-24 18:55:08
● 2026-08-06 15:27:58

●MXalt3.aspmx.l.google.com2019-03-10 → 2026-08-06 · 3 obs

○ 2017-02-20 03:24:40
● 2019-03-10 22:41:50
● 2026-08-06 15:27:58

●MXalt4.aspmx.l.google.com2019-03-10 → 2026-08-06 · 3 obs

○ 2017-02-20 03:24:40
● 2019-03-10 22:41:50
● 2026-08-06 15:27:58

●MXaspmx.l.google.com2016-04-24 → 2026-08-06 · 3 obs

○ 2016-01-29 12:13:46
● 2016-04-24 18:55:08
● 2026-08-06 15:27:58

○MXaspmx2.googlemail.com2016-04-24 → 2017-02-20 · 5 obs

○ 2016-01-29 12:13:46
● 2016-04-24 18:55:08
● 2017-02-20 03:24:40
○ 2019-03-10 22:41:50
○ 2026-08-06 15:27:58

○MXaspmx3.googlemail.com2016-04-24 → 2017-02-20 · 5 obs

○ 2016-01-29 12:13:46
● 2016-04-24 18:55:08
● 2017-02-20 03:24:40
○ 2019-03-10 22:41:50
○ 2026-08-06 15:27:58

○MXmail.secureserver.net2016-04-24 → 2017-02-20 · 5 obs

○ 2016-01-29 12:13:46
● 2016-04-24 18:55:08
● 2017-02-20 03:24:40
○ 2019-03-10 22:41:50
○ 2026-08-06 15:27:58

○MXmailstore1.secureserver.net2015-06-09 → 2016-01-29 · 4 obs

● 2015-06-09 10:56:08
● 2016-01-29 12:13:46
○ 2016-04-24 18:55:08
○ 2026-08-06 15:27:58

○MXsmtp.secureserver.net2015-06-09 → 2017-02-20 · 4 obs

● 2015-06-09 10:56:08
● 2017-02-20 03:24:40
○ 2019-03-10 22:41:50
○ 2026-08-06 15:27:58

●A192.185.24.172019-03-10 → 2026-08-06 · 3 obs

○ 2017-02-20 03:24:40
● 2019-03-10 22:41:50
● 2026-08-06 15:27:58

○A50.63.202.82015-06-09 → 2017-02-20 · 4 obs

● 2015-06-09 10:56:08
● 2017-02-20 03:24:40
○ 2019-03-10 22:41:50
○ 2026-08-06 15:27:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net...	-
bf9connect.com	ns313.websitewelcome.com, ns314.websitewelcome.com	2 records

✅ Authoritative Response

Server:192.185.24.135

NS records: ns313.websitewelcome.com, ns314.websitewelcome.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bf9connect.com (unsigned zone)

⏱️ Timing

Total: 180ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`192.185.24.17`
NS	2	`ns314websitewelcome.com, ns313.websitewelcome.com`
MX	5	`aspmx.l.google.com (pri: 1), alt2.aspmx.l.google.com (pri: 5)...`
TXT	1	`v=spf1 a mx include:websitewelcome.com ~`
SOA	1	`ns313.websitewelcome.com jessica.insalac`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns313.websitewelcome.com, ns314.websitewelcome.com)

Analysis

IP Addresses

bf9connect.com resolves to one IP address: 192.185.24.17.

bf9connect.com shares its IP numbers with other host names like blubirdinteractive.biz, mbsclawyers.com and mail.mytravelguy.net.

Name Servers

bf9connect.com is delegated to three name servers: ns314websitewelcome.com, ns313.websitewelcome.com and ns314.websitewelcome.com.

bf9connect.com has at least partial name server overlap with other domains, such as grandsterlingusa.com, nightmill.com, xtensor.co and two others.

ns313.websitewelcome.com directs to 192.185.24.134 and ns314.websitewelcome.com directs to 192.185.24.135; each host name points to exactly one IP number.

Mail Servers

Mail for bf9connect.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

bf9connect.com has at least partial mail server overlap with other domains such as ns500759.ns500758.ns500698.ns500736.ns500735.ns500708.ns500708.ns500576.ns500698.ns500576.tracksymphony.com, ns500821.ns500794.ns500794.ns500794.ns500794.ns500794.ns500821.ns500794.ns500821.ns500821.ns500795.ns500795.ns500790.ns500795.lustypartnersfinder.com, ns500765.ns500699.ns500734.ns500734.ns500699.ns500699.ns500588.ns500693.ns500588.ns500693.ns500588.ns500588.ns500632.ns500612.ns500612.ns500578.ns500110.dtrkdll.com and two more.

These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com points to 142.250.31.26 and 2607:f8b0:4004:c06::1a.

alt1.aspmx.l.google.com points to 108.177.123.27 and 2800:3f0:4003:c0f::1b.

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

alt3.aspmx.l.google.com points to 192.178.223.27 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com points to 172.253.157.27 and 2a00:1450:400c:c23::1a.