bfp.cl - robtex.com

bfp.cl

DNSSEC⚠️ Not signed
NSns1.hostname.cl ⚠️ Not in zone NS records
A201.159.174.100πŸ‡¨πŸ‡± HostnameCL201.159.174.0/24 This route object is for IFX Networks customer route which is being exported under this origin AS 262256
NSns2.hostname.cl ⚠️ Not in zone NS records
A64.120.17.98πŸ‡ΊπŸ‡Έ LEASEWEB-USA-SEA-1164.120.16.0/22 Leaseweb USA, Inc.
NSns3.hostname.cl ⚠️ Not in zone NS records
A190.110.120.101πŸ‡¨πŸ‡± HostnameCL190.110.120.0/24 This route object is for IFX Networks customer route which is being exported under this origin AS 262256
NSns4.hostname.cl ⚠️ Not in zone NS records

cl

DNSSEC⚠️ Not signed
NSa.nic.cl ⭐
NSb.nic.cl
NSc.nic.cl
NScl-ns.anycast.pch.net
NScl1-tld.d-zone.ca
NScl1.dnsnode.net
NScl2-tld.d-zone.ca
TXTINFO=CL zone generated Mon Jul 13 18:30:02 -04 2026
SOAa.nic.cldnsadmin@nic.cl 2026-07-13 #37

Previously MX for

Same first word

Similar names

DNS History

7 records (4 active, 3 former)

20162017201820192020202120222023202420252026NSns1.hostname.clns2.hostname.clns3.hostname.clns4.hostname.clMXbfp.clA190.110.123.220190.196.69.220
●NSns1.hostname.cl2015-07-14 β†’ 2026-07-13 Β· 2 obs
● 2015-07-14 09:39:00
● 2026-07-13 23:10:22
●NSns2.hostname.cl2015-07-14 β†’ 2026-07-13 Β· 2 obs
● 2015-07-14 09:39:00
● 2026-07-13 23:10:22
●NSns3.hostname.cl2026-05-07 β†’ 2026-07-13 Β· 3 obs
β—‹ 2015-07-14 09:39:00
● 2026-05-07 06:11:38
● 2026-07-13 23:10:22
●NSns4.hostname.cl2026-05-07 β†’ 2026-07-13 Β· 3 obs
β—‹ 2015-07-14 09:39:00
● 2026-05-07 06:11:38
● 2026-07-13 23:10:22
β—‹MXbfp.cl2015-07-14 β†’ 2021-02-17 Β· 4 obs
● 2015-07-14 09:39:00
● 2021-02-17 17:01:18
β—‹ 2026-05-07 06:11:38
β—‹ 2026-07-13 23:10:22
β—‹A190.110.123.2202016-06-22 β†’ 2021-02-17 Β· 5 obs
β—‹ 2016-04-06 06:36:24
● 2016-06-22 08:18:28
● 2021-02-17 17:01:18
β—‹ 2026-05-07 06:11:38
β—‹ 2026-07-13 23:10:22
β—‹A190.196.69.2202015-07-14 β†’ 2016-04-06 Β· 4 obs
● 2015-07-14 09:39:00
● 2016-04-06 06:36:24
β—‹ 2016-06-22 08:18:28
β—‹ 2026-07-13 23:10:22

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
cla.nic.cl, b.nic.cl, c.nic.cl, cl1.dnsnode.net...14 records
bfp.clns4.hostname.cl, ns3.hostname.cl, ns1.hostname.cl, ns2.hostname.cl4 records

βœ… Authoritative Response

Server:64.120.17.98

NS records: ns4.hostname.cl, ns3.hostname.cl, ns1.hostname.cl, ns2.hostname.cl

πŸ”’ DNSSEC Status

❌ Bogus (DNSSEC validation failed)

Validation error at cl: Error: DNS query timeout: 190.124.27.10 for DNSKEY cl

⏱️ Timing

Total: 3510ms | Queries: -

πŸ“„ Records

TypeCountSample Data

πŸ“Œ Glue Records Collected

Total: 18

In-bailiwick: 6 (a.nic.cl, a.nic.cl, b.nic.cl...)

Out-of-bailiwick: 12 (cl1.dnsnode.net, cl1.dnsnode.net, cl-ns.anycast.pch.net...)

Analysis

Name Servers

Four name servers handle the delegation for bfp.cl: ns1.hostname.cl, ns2.hostname.cl, ns3.hostname.cl and ns4.hostname.cl.

bfp.cl partially shares its NS delegation with several other domains, including comercialtodomaq.cl, www.nv.cl, elsultan.cl and two others.

In DNS configurations, these name servers often share authority with ns1.hn.cl, secundario.nic.cl, ns1.inc.cl and 6 other name servers.

ns1.hostname.cl, ns2.hostname.cl and ns3.hostname.cl each resolve to a single IP address: ns1.hostname.cl resolves to 201.159.174.100, ns2.hostname.cl resolves to 64.120.17.98 and ns3.hostname.cl resolves to 190.110.120.101.