dbfmp.com - dns.ninja

`dbfmp.com`

DNSSEC	⚠️ Not signed
A	2a02:4780:6:1862:0:2431:9625:3^{🇮🇩 IIHOS0012a02:4780:6::/48 HOSTINGER ID}
A	145.223.108.216^{🇳🇱 IIHOS001145.223.108.0/22 HOSTINGER ID}
NS	`ns1.dns-parking.com` ⭐
		A	2400:cb00:2049:1::a29f:18c9^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.24.201^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dns-parking.com`
NS	`ns2.dns-parking.com`
		A	2400:cb00:2049:1::a29f:192a^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.25.42^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dns-parking.com`
MX	`mx1.hostinger.com` ⭐
		A	2606:4700:90:0:c1f8:f874:2386:b61f^{🇺🇸 Cloudflare2606:4700:90::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.65.182.103^{🇺🇸 Cloudflare172.65.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`mx2.hostinger.com`⁽¹⁰⁾
		A	2606:4700:90:0:c1f8:f874:2386:b61f^{🇺🇸 Cloudflare2606:4700:90::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.65.182.103^{🇺🇸 Cloudflare172.65.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
TXT	`v=spf1 include:_spf.mail.hostinger.com ~all`
SOA	`ns1.dns-parking.com`dns@hostinger.com 2026-07-09 #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=1783728062

Previously MX for

dbfmp.com

Same first word

dbfmp.com

dbfmp.cn

Similar names

pbmdf.com

dpfmb.com

pdfbm.cn

mdpfb.net

bpmfd.com

dmbpf.com

pfbmd.com

mdbpf.com

bmpdf.com

bfpmd.com

pmfdb.cn

pbmdf.co.kr

bpdfm.com

fmbdp.com

DNS History

16 records (6 active, 10 former)

○NSjm1.dns.com2020-02-06 → 2020-02-06 · 4 obs

○ 2017-02-19 02:41:14
● 2020-02-06 23:22:02
○ 2026-02-16 03:59:48
○ 2026-07-11 00:19:54

○NSjm2.dns.com2020-02-06 → 2020-02-06 · 4 obs

○ 2017-02-19 02:41:14
● 2020-02-06 23:22:02
○ 2026-02-16 03:59:48
○ 2026-07-11 00:19:54

○NSjuming.dnsdun.com2017-02-19 → 2017-02-19 · 4 obs

○ 2016-04-07 16:56:56
● 2017-02-19 02:41:14
○ 2020-02-06 23:22:02
○ 2026-07-11 00:19:54

○NSjuming.dnsdun.net2017-02-19 → 2017-02-19 · 4 obs

○ 2016-04-07 16:56:56
● 2017-02-19 02:41:14
○ 2020-02-06 23:22:02
○ 2026-07-11 00:19:54

●NSns1.dns-parking.com2026-02-16 → 2026-07-11 · 3 obs

○ 2020-02-06 23:22:02
● 2026-02-16 03:59:48
● 2026-07-11 00:19:54

○NSns1.idwebhost.com2015-07-26 → 2016-04-07 · 4 obs

● 2015-07-26 11:02:52
● 2016-04-07 16:56:56
○ 2017-02-19 02:41:14
○ 2026-07-11 00:19:54

●NSns2.dns-parking.com2026-02-16 → 2026-07-11 · 3 obs

○ 2020-02-06 23:22:02
● 2026-02-16 03:59:48
● 2026-07-11 00:19:54

○NSns2.idwebhost.com2015-07-26 → 2016-04-07 · 4 obs

● 2015-07-26 11:02:52
● 2016-04-07 16:56:56
○ 2017-02-19 02:41:14
○ 2026-07-11 00:19:54

○MXdbfmp.com2015-07-26 → 2016-04-07 · 4 obs

● 2015-07-26 11:02:52
● 2016-04-07 16:56:56
○ 2017-02-19 02:41:14
○ 2026-07-11 00:19:54

●MXmx1.hostinger.com2026-02-16 → 2026-07-11 · 3 obs

○ 2017-02-19 02:41:14
● 2026-02-16 03:59:48
● 2026-07-11 00:19:54

●MXmx2.hostinger.com2026-02-16 → 2026-07-11 · 3 obs

○ 2017-02-19 02:41:14
● 2026-02-16 03:59:48
● 2026-07-11 00:19:54

●A145.223.108.2162026-02-16 → 2026-07-11 · 3 obs

○ 2020-02-06 23:22:02
● 2026-02-16 03:59:48
● 2026-07-11 00:19:54

○A154.214.166.152020-02-06 → 2020-02-06 · 4 obs

○ 2017-02-19 02:41:14
● 2020-02-06 23:22:02
○ 2026-02-16 03:59:48
○ 2026-07-11 00:19:54

○A202.52.146.402015-07-26 → 2016-04-07 · 4 obs

● 2015-07-26 11:02:52
● 2016-04-07 16:56:56
○ 2017-02-19 02:41:14
○ 2026-07-11 00:19:54

○A23.89.17.622017-02-19 → 2017-02-19 · 4 obs

○ 2016-04-07 16:56:56
● 2017-02-19 02:41:14
○ 2020-02-06 23:22:02
○ 2026-07-11 00:19:54

●A2a02:4780:6:1862:0:2431:9625:32026-02-16 → 2026-07-11 · 3 obs

○ 2020-02-06 23:22:02
● 2026-02-16 03:59:48
● 2026-07-11 00:19:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
dbfmp.com	ns1.dns-parking.com, ns2.dns-parking.com	4 records

✅ Authoritative Response

Server:162.159.25.42

NS records: ns1.dns-parking.com, ns2.dns-parking.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dbfmp.com (unsigned zone)

⏱️ Timing

Total: 240ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`145.223.108.216`
AAAA	1	`2a02:4780:6:1862:0:2431:9625:3`
NS	2	`ns2.dns-parking.com, ns1.dns-parking.com`
MX	2	`mx2.hostinger.com (pri: 10), mx1.hostinger.com (pri: 5)`
TXT	1	`v=spf1 include:_spf.mail.hostinger.com ~`
SOA	1	`ns1.dns-parking.com dns.hostinger.com`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.dns-parking.com, ns1.dns-parking.com, ns2.dns-parking.com...)

Analysis

IP Addresses

dbfmp.com points to the IP addresses 145.223.108.216 and 2a02:4780:6:1862:0:2431:9625:3

Other hosts including datafmp.com, tfdirectory.co.uk and aljihad.sch.id share IP addresses with dbfmp.com.

Name Servers

Two name servers handle the delegation for dbfmp.com: ns1.dns-parking.com and ns2.dns-parking.com.

dbfmp.com shares its name server setup with other domains, including kelvinrush.com, parivahansewa.pro, wundercloud.com and two others.

ns1.dns-parking.com and ns2.dns-parking.com both carry two IP addresses. The A records for ns1.dns-parking.com are 162.159.24.201 and 2400:cb00:2049:1::a29f:18c9; the A records for ns2.dns-parking.com are 162.159.25.42 and 2400:cb00:2049:1::a29f:192a.

Mail Servers

dbfmp.com has two mail servers: mx1.hostinger.com and mx2.hostinger.com.

dbfmp.com shares the same mail server setup as other domains, including deftnote.com, dxpone.com, casadoconvite.com.br and two others.

dbfmp.com uses mail servers that are also used by other domains, including syndic.co.in, dahviral.com and healthnhealthy.com.

mx1.hostinger.com and mx2.hostinger.com each point to two IP numbers — 172.65.182.103 and 2606:4700:90:0:c1f8:f874:2386:b61f — making both hosts identical in their DNS resolution.

mx1.hostinger.com along with mx2.hostinger.com each resolve to 2606:4700:90:0:c1f8:f874:2386:b61f IP addresses.

mx1.hostinger.com along with mx2.hostinger.com each resolve to 172.65.182.103 IP addresses.