Website DNS

Website DNS

Check the DNS record of the website online using this tool

Website DNS

Type Host Class Target TTL
A bfcm2021.shop. IN 198.54.125.84 7192
NS bfcm2021.shop. IN dns2.namecheaphosting.com. 86400
NS bfcm2021.shop. IN dns1.namecheaphosting.com. 86400
MX bfcm2021.shop. IN 5 mx1-hosting.jellyfish.systems. 14400
MX bfcm2021.shop. IN 10 mx2-hosting.jellyfish.systems. 14400
MX bfcm2021.shop. IN 20 mx3-hosting.jellyfish.systems. 14400
TXT bfcm2021.shop. IN "v=spf1 +a +mx +ip4:68.65.121.137 include:spf.web-hosting.com ~all" 14400

Last update on 2026-11-08 18:57:34

bfcm2021.shop - bfcm2021 المصادر والمعلومات.

bfcm2021.shop - bfcm2021 المصادر والمعلومات.

Title
bfcm2021.shop - bfcm2021 المصادر والمعلومات.
Description
bfcm2021.shop هل هو أول وأفضل مصادر جميع المعلومات التي تبحث عنها. من ضوء الموضوعات العامة إلى مزيد من الموضوعات التي كنت لتتوقعها هنا، bfcm2021.shop تمتلكها جميعًا. نأمل أن تجد ما تبحث عنه!
Image
bfcm2021.shop - bfcm2021 المصادر والمعلومات.

Enter a domain and this tool queries its DNS records directly: A/AAAA for IP addresses, MX for mail routing, TXT for verification and SPF/DKIM records, NS for nameservers, and more. It's built for confirming a DNS change has actually propagated, or figuring out why email or a site isn't resolving the way it should.

Enter a domain like this to see its live DNS records:

example.com → A, MX, NS, TXT and other records currently published for that domain

Why don't I see my recent DNS change yet?

DNS changes take time to propagate because of caching (TTL) at resolvers around the world. A change can take anywhere from a few minutes to about 48 hours to show up everywhere.

What does an MX record tell me?

It tells you which mail servers are responsible for receiving email for that domain, in priority order.

Why would a domain have multiple TXT records?

TXT records get used for several unrelated things at once: domain verification, SPF for email senders, DKIM keys, and more. So a domain often ends up with several.

Does this tool query my own DNS cache?

No, it queries DNS records directly, so it reflects what is actually published, independent of any caching on your own device or network.