🔍
Bulk DNS Lookup
Professional tool from DPS.MEDIA
DPS.MEDIA
Digital Tools
Nhập mỗi tên miền một dòng (có thể dán URL). Chọn loại bản ghi hoặc "TẤT CẢ" để tra 5 loại phổ biến.
0 domains
Loại Bản Ghi:
Delay between requests:
ms
⚠️
📊
Sẵn sàng tra cứu bản ghi DNS...
Powered by DPS.MEDIA

`;const ta = root.querySelector('#dns-lines'); const btnRun = root.querySelector('#dns-run'); const btnStop = root.querySelector('#dns-stop'); const btnClear = root.querySelector('#dns-clear'); const typesWrap = root.querySelector('#dns-types'); const statusEl = root.querySelector('#dns-status'); const errorEl = root.querySelector('#dns-error'); const errorTextEl = root.querySelector('#dns-error-text'); const resultsEl = root.querySelector('#dns-results'); const delayInput = root.querySelector('#dns-delay'); const btnCopy = root.querySelector('#dns-copy-table'); const countEl = root.querySelector('#dns-count'); const progressEl = root.querySelector('#dns-progress'); const progressBarEl = root.querySelector('#dns-progress-bar'); const runTextEl = root.querySelector('#run-text');// Type pills với DPS branding const TYPE_LABELS = { 'ALL': 'TẤT CẢ', 'A': 'A', 'CNAME': 'CNAME', 'MX': 'MX', 'NS': 'NS', 'TXT': 'TXT' };let activeType = 'A'; RECORDS.forEach(t => { const b = document.createElement('button'); b.textContent = TYPE_LABELS[t] || t; b.className = 'dns-type-btn'; if (t === activeType) { b.classList.add('active'); } b.addEventListener('click',()=>{ if (isRunning) return; activeType = t; [...typesWrap.children].forEach(c => c.classList.remove('active')); b.classList.add('active'); }); typesWrap.appendChild(b); });// Domain count tracker với DPS colors function updateDomainCount() { const domains = ta.value.split(/\r?\n/) .map(s=>extractHostname(s)) .filter(Boolean); countEl.textContent = `${domains.length} tên miền`; if (domains.length > 100) { countEl.style.background = 'rgba(220,38,38,0.9) !important'; countEl.style.color = 'white !important'; } else if (domains.length > 50) { countEl.style.background = 'rgba(245,158,11,0.9) !important'; countEl.style.color = 'white !important'; } else if (domains.length > 0) { countEl.style.background = 'rgba(50,181,97,0.9) !important'; countEl.style.color = 'white !important'; } else { countEl.style.background = 'rgba(21,21,119,0.9) !important'; countEl.style.color = 'white !important'; } }ta.addEventListener('input', updateDomainCount); updateDomainCount();function clampDelay(){ let v = Number(delayInput.value || 0); if (!Number.isFinite(v) || v { if (e.key === '-') e.preventDefault(); });function extractHostname(input){ if(!input) return ''; try{ return new URL(input).hostname.replace(/\.$/,''); } catch(e){ return String(input).trim().replace(/^https?:\/\//i,'').replace(/^\/*/,'').split('/')[0].split('?')[0].replace(/\.$/,''); } }function sleep(ms){ return new Promise(r=>setTimeout(r, ms)); }function clearError(){ errorEl.style.display='none'; errorTextEl.textContent=''; } function showError(msg){ errorEl.style.display='flex'; errorTextEl.textContent=msg; } function setStatus(msg){ statusEl.textContent = msg; }function updateProgress(current, total) { if (total === 0) { progressEl.style.display = 'none'; return; } progressEl.style.display = 'block'; const percentage = Math.min((current / total) * 100, 100); progressBarEl.style.width = `${percentage}%`; }// Render table với DPS branding - Sử dụng div thay vì table elements function ensureTable(){ if(resultsEl.firstChild && resultsEl.firstChild.classList && resultsEl.firstChild.classList.contains('dns-table')) return resultsEl.firstChild; resultsEl.innerHTML = ''; const table = document.createElement('div'); table.className = 'dns-table'; const isMobile = window.innerWidth

Domain Name
Eliminate
Name
TTL
Data

`; resultsEl.appendChild(table); return table; }const allRows = []; function appendRows(rows){ const table = ensureTable(); const tbody = table.querySelector('.dns-table-body'); const frag = document.createDocumentFragment(); const isMobile = window.innerWidth { allRows.push(r); const tr = document.createElement('div'); tr.className = 'dns-table-row'; let dataColor = '#374151'; if (r.data === '(không có dữ liệu)') dataColor = '#9ca3af'; else if (r.data && r.data.startsWith('Lỗi:')) dataColor = '#dc2626'; tr.innerHTML = `

${r.domain}
${r.type}
${r.name||''}
${r.ttl??''}
${r.data||''}

`; frag.appendChild(tr); }); tbody.appendChild(frag); btnCopy.disabled = false; btnCopy.classList.remove('success'); }async function queryDoH(domain, type){ const base = 'https://dns.google/resolve'; const params = new URLSearchParams(); params.set('name', domain); params.set('type', TYPE_CODE[type]); const url = `${base}?${params.toString()}`; const res = await fetch(url, { headers: { 'Accept':'application/json' }}); if(!res.ok) throw new Error(`HTTP ${res.status}`); return await res.json(); }let abortFlag = false; let isRunning = false;btnStop.addEventListener('click', ()=>{ abortFlag = true; setStatus('🛑 Đang dừng...'); });btnClear.addEventListener('click', () => { if (isRunning) return; resultsEl.innerHTML = `

📊
Sẵn sàng tra cứu bản ghi DNS...
Powered by DPS.MEDIA

`; allRows.length = 0; btnCopy.disabled = true; btnCopy.classList.remove('success'); clearError(); setStatus(''); progressEl.style.display = 'none'; });btnRun.addEventListener('click', async ()=>{ if (isRunning) return; clearError(); allRows.length = 0; abortFlag = false; isRunning = true;btnRun.disabled = true; runTextEl.textContent = '⏳ Đang chạy...'; btnStop.style.display = 'block'; btnClear.style.display = 'none'; [...typesWrap.children].forEach(b => { b.style.cursor = 'not-allowed'; b.style.opacity = '0.6'; });const delay = clampDelay();const domains = ta.value.split(/\r?\n/) .map(s=>extractHostname(s)) .filter(Boolean);if (!domains.length){ showError('Vui lòng nhập ít nhất 1 tên miền.'); resetUIState(); return; } if (domains.length > 100){ showError('Giới hạn 100 tên miền mỗi lần để tránh quá tải. Hãy chia nhỏ danh sách.'); resetUIState(); return; }const types = (activeType==='ALL') ? [...POPULAR] : [activeType]; const totalQueries = domains.length * types.length;resultsEl.innerHTML = ''; ensureTable();let completed = 0; for (let i=0; i 0){ const rows = json.Answer.map(a=>({ domain:d, type:t, name:a.name, ttl:a.TTL, data:a.data })); appendRows(rows); } else if (json && Array.isArray(json.Authority) && json.Authority.length > 0){ const rows = json.Authority.map(a=>({ domain:d, type:t, name:a.name, ttl:a.TTL, data:a.data })); appendRows(rows); } else { appendRows([{ domain:d, type:t, name:'', ttl:'', data:'(không có dữ liệu)' }]); } }catch(e){ appendRows([{ domain:d, type:t, name:'', ttl:'', data:`Lỗi: ${e.message}` }]); } completed++; updateProgress(completed, totalQueries); if (completed { b.style.cursor = 'pointer'; b.style.opacity = '1'; }); }function escapeCell(v){ if (v == null) return ''; const s = String(v); return s.replace(/\t/g, ' ').replace(/\r?\n/g, ' '); } function rowsToTSV(rows){ const header = ['Tên Miền','Loại','Tên','TTL','Dữ Liệu']; const lines = [header.join('\t')].concat(rows.map(r => [r.domain, r.type, r.name||'', r.ttl??'', r.data||''].map(escapeCell).join('\t'))); return lines.join('\n'); } async function copyText(text){ if (navigator.clipboard && navigator.clipboard.writeText){ await navigator.clipboard.writeText(text); } else { const ta = document.createElement('textarea'); ta.value = text; document.body.appendChild(ta); ta.select(); document.execCommand('copy'); document.body.removeChild(ta); } } btnCopy.addEventListener('click', async ()=>{ if (!allRows.length){ setStatus('❌ Không có dữ liệu để sao chép.'); return; } try{ await copyText(rowsToTSV(allRows)); setStatus('✅ Đã sao chép bảng vào clipboard!'); const originalText = btnCopy.textContent; btnCopy.textContent = '✅ Đã sao chép!'; btnCopy.classList.add('success'); setTimeout(() => { btnCopy.textContent = originalText; btnCopy.classList.remove('success'); }, 2000); }catch(e){ setStatus('❌ Sao chép thất bại: ' + e.message); } });// Window resize handler let resizeTimeout; window.addEventListener('resize', () => { clearTimeout(resizeTimeout); resizeTimeout = setTimeout(() => { if (resultsEl.firstChild && resultsEl.firstChild.classList && resultsEl.firstChild.classList.contains('dns-table')) { const currentRows = [...allRows]; allRows.length = 0; resultsEl.innerHTML = ''; if (currentRows.length > 0) { appendRows(currentRows); } } }, 100); });// Initialize copy button state btnCopy.disabled = true; })();Standard DNS configuration helps increase website loading speed by up to 30%, while also ensuring security against common cyber attacks.

According to a survey by Akamai, 53% of users leave a page if it takes more than 3 seconds to load. DPS.MEDIA Always emphasize that DNS optimization is the first step of a successful digital marketing strategy.
The importance of DNS in user experience and website performance

The importance of DNS in user experience and website performance

How does DNS affect page load speed?

When users access a website, the first process that occurs is DNS lookup. The system will convert the domain name to an IP address to connect to the server. The average DNS lookup time accounts for 10-30% of the total page load time (according to Cloudflare data, 2023).

A non-optimized DNS can cause the website to:
– Increase TTFB (Time To First Byte)
– Cause delays during redirection
– Negatively affect SEO and user experience

TIP: Use globally distributed DNS such as Cloudflare, Google DNS to reduce geographic latency.

The impact of DNS on website security

DNS is the “initial link” in every connection, so protecting it cannot be ignored. A misconfigured DNS can be:
– DNS spoofing attack - redirecting users to fake websites
– Internal information leak via subdomains
– Denial of service (DDoS) through DNS Resolver exploitation

According to a report from Cisco (2022), 91% of malware attacks use DNS at some stage.

Checklist: Effective DNS configuration for website owners

  • Choose reputable DNS providers (Google DNS, Cloudflare, dnspod...)
  • Enable DNSSEC to authenticate queries
  • Use Anycast feature to increase global stability
  • Hide DNS information with proxy forwarding services
  • Monitor DNS response time with tools like Pingdom, GTmetrix

Comparison table of DNS providers' response times

DNS providerAverage response time (ms)
Google DNS (8.8.8.8)22ms
Cloudflare DNS (1.1.1.1)13ms
OpenDNS28ms

Source: DNSPerf, Report Q1/2023

Case study: Reducing page load speed from 4.2s to 2.1s

A retail business in Ho Chi Minh City used domestic hosting but international DNS was not distributed. After switching to Cloudflare DNS and enabling DNSSEC, the DNS lookup metric dropped from 560ms to 120ms. At the same time, the bounce rate decreased by nearly 17% after just 2 weeks of implementation.

Warning: Using multiple DNS providers in parallel without properly configuring SRV records can cause random connection loss errors.

Takeaway

DNS is the first link that creates website performance and security. An improperly configured DNS not only slows down the website but also expands security risks. Start optimizing DNS like optimizing a server – today.
Choose a reputable DNS provider to enhance security and response speed

Choosing a reputable DNS provider to enhance security and response speed

Why is choosing a reliable DNS crucial?

Choosing the right DNS provider can improve up to 30-70% DNS response speed, which is a key factor in user experience and SEO. According to Cloudflare (DNS Performance Report 2022), a delay of just 100ms at the DNS layer can significantly affect bounce rates.

Besides speed, the DNS system is the first line of defense for website security. Weak DNS is easily targeted by forms of DDoS attacks, DNS spoofing, or cache poisoning.

TIP: Prioritize DNS providers that support DNSSEC and have data centers near your target market.

Criteria for selecting a DNS provider

Below are the factors to consider:

Global DNS query speed: Prioritize providers like Cloudflare, AWS Route 53, or Google Cloud DNS.
Protection capability: Supports DNSSEC, DDoS protection, integrated DNS firewall.
Scalability & self-healing: Multiple PoPs (Points of Presence) worldwide.
DNS management UX/UI: Clear dashboard, easy record updates.

Comparison of some popular DNS providers

ProviderDNSSECGlobal PoPAverage response time (ms)
CloudflareYes200+15
Google Cloud DNSYes150+22
godaddy DNSNo15+65

Source: DNSPerf Reports 2023

Checklist: How to implement new DNS safely & effectively

– [ ] Test new DNS on staging before applying to production
– [ ] Activate DNSSEC (if supported by the provider)
– [ ] Check propagation with DNS Checker tools or dig
– [ ] Turn on Notify/Monitoring if the system has downtime

Case study: Interior e-commerce website in Vietnam

A DPS.MEDIA client in the furniture sector switched DNS from the default provider to Cloudflare (2023). Result: DNS response time dropped from 120ms to under 20ms, DNS downtime rate decreased by 96%. The migration took only 30 minutes with no service interruption.

Note: Some free DNS services are easily limited in scalability when traffic spikes suddenly.

Takeaway: Choosing the right DNS not only helps the website run faster but also acts as an early shield against cyber security threats. The DNS provider is the ”backbone” for your entire online system.
Accurate DNS record setup helps optimize traffic and reduce latency

Accurate DNS record setup helps optimize traffic and reduce latency

How DNS records affect page load performance

Accurately configuring records like A record, CNAME, and TTL helps browsers query faster and reduces unnecessary lookups. For example, changing TTL from 86400 seconds to 3600 can reduce update wait time to under 1 hour.

According to Cloudflare's report (2022), using high-performance DNS can reduce page load latency by up to 20-40% in Southeast Asia.

Tip: Avoid pointing CNAME to slow servers or those without CDN; prioritize Anycast DNS platforms like Cloudflare or Google DNS.

Important DNS records that need correct configuration

Below are common records that need to be configured carefully:

  • A record: Point to the correct main server IP
  • CNAME: Used to point subdomains to the main domain
  • MX record: Ensure business email is not interrupted
  • TXT record (SPF, DKIM): Secure email sending, prevent spam

Standard DNS setup checklist

  • ✔ Check that the A record points to the correct server IP
  • ✔ Set an appropriate TTL (1h-6h for frequently updated sites)
  • ✔ Enable DNSSEC (if supported by your provider)
  • ✔ Ensure all subdomains have accurate SPF records

Case study: Changing records helps reduce response time by 35%

An E-learning customer changed their CNAME record from a free DNS service to Cloudflare Pro. After 7 days, using the WebPageTest tool, average latency decreased from 320ms to 205ms – a 35% reduction. No backend code changes.

ParametersBeforeAfter
DNS Resolution Time320ms205ms
CDN RoutingNoneYes

Common risks when misconfiguring DNS

  • Warning: Incorrect A record configuration can cause the website to go offline immediately
  • TTL set too low causes continuous queries, affecting DNS performance
  • Incorrect SPF record can cause emails to be blocked or marked as spam

Tip: After each DNS change, use tools like dig, nslookup, or dnschecker.org to verify that the record has been updated correctly.

Takeaway:

Accurate DNS setup is the foundation for a fast-loading, secure, and stable website. Optimize every record – starting from the A record configuration – to maximize response time efficiency and ensure continuous user experience.
Implement DNSSEC to protect your website from spoofing and fake DNS attacks

Implementing DNSSEC to protect your website from spoofing and fake DNS attacks

What is DNSSEC and why is it necessary?

DNSSEC (Domain Name System Security Extensions) is a set of extensions to traditional DNS protocols that helps authenticate the origin of DNS data.

Without DNSSEC:

– DNS data is vulnerable to “man-in-the-middle” attacks”
– Hackers can redirect access to fake websites
– End users find it difficult to distinguish the real website

According to the Global Cyber Alliance 2023 report, 29% of DNS phishing incidents are due to improper DNSSEC implementation.

TIP: Implementing DNSSEC does not speed up page loading, but it increases website reliability in terms of domain name security.

Practical benefits of applying DNSSEC

Organizations that have implemented DNSSEC report:

– Reduces 40-60% risk of domain spoofing (According to Verisign, 2021)
– When combined with HTTPS and HSTS, system reliability increases significantly
– Helps increase credibility when registering security services (SSL/TLS, DMARC...)

A real-world example: A mid-sized e-commerce business in Ho Chi Minh City experienced a DNS spoofing incident in 2022, causing nearly 12% of access over 3 days to be redirected to a phishing website – this incident was completely resolved after activating DNSSEC on Cloudflare DNS.

Simple steps to implement DNSSEC

Implementation checklist for popular DNS systems:

  • ✅ Verify that your DNS provider supports DNSSEC (GoDaddy, Cloudflare, etc.)
  • ✅ Enable DNSSEC in the DNS control panel
  • ✅ Update the DS Record on the domain management system (such as VNNIC or Namecheap)
  • ✅ Check DNS signature authentication using tools like dig or dnsviz.net
DNS ProviderDNSSEC SupportEasy Deployment
CloudflareAvailable✔️ With just 1 toggle
Google DomainsYes✔️ Automatic Configuration
GoDaddyPremium Package⚠️ Additional purchase required

Considerations before deployment

– Incorrect DS Record deployment can make the website inaccessible
– Requires coordination between the DNS administrator and the domain registrar
– Backup old DNS configurations to rollback if issues occur

DPS.MEDIA recommends SMEs test DNSSEC in a test environment before rolling it out system-wide.

Takeaway: DNSSEC is not just a security standard, but also an important step to protect customer trust in the “zero trust” era.

Use CDN combined with DNS configuration to improve page load speed in all regions

Using CDN combined with DNS configuration to improve page load speed in all regions

Reasons to combine CDN and smart DNS

CDN (Content Delivery Network) helps distribute content through servers closest to users, reducing latency when accessing.
– DNS is the first layer determining the routing speed to the CDN server - if configured correctly, retrieval time is significantly reduced.
– According to a report from Cloudflare (2023), average page load time is shortened by 30-45% when there is good coordination between CDN and distributed DNS architecture.

TIP: Always choose a DNS provider with global infrastructure coverage and Anycast support (such as Cloudflare or Google DNS) to optimize routing.

Checklist for effective CDN & DNS configuration

  • ✔ Set up a CDN such as Cloudflare, Akamai, or BunnyCDN, prioritizing servers in the target region.
  • ✔ Point the domain to an intermediary DNS integrated with CDN (or use a custom DNS that supports low TTL).
  • ✔ Enable automatic static caching and GZIP compression from the CDN side.
  • ✔ Configure Domain CNAME or A record to ensure compatibility and avoid timeouts.
  • ✔ Check DNS propagation using tools like What's my DNS to evaluate stability.

DNS configuration illustration combined with CDN (HTML Table)

Record TypeValueFunction
A record192.0.2.1Point to the original CDN IP address
CNAMEcdn.example.comPoint subdomain to CDN resources
TTL300sReduce DNS update latency

Real-world examples & effectiveness

A customer in Da Nang using DPS.MEDIA combined with Global CDN and Anycast DNS improved page load time from 4.2s to 1.7s (measured by GTmetrix). International traffic increased by 561% after 30 days of deployment—thanks to improved access from the US and Japan.

NOTE: Not all CDNs are fully compatible with your current DNS system. You should test partitioning before large-scale deployment.

Brief takeaway

Optimal combination between CDN and smart DNS helps speed up global website loading and reduces pressure on the origin server. This is a technical foundation that should be prioritized early in a sustainable website acceleration strategy.
Monitor and regularly update DNS configuration to ensure continuous and stable operation

Monitor and periodically update DNS configuration to ensure continuous and stable operation

Why is it necessary to monitor DNS regularly?

Monitoring DNS configuration not only helps detect issues early but also maintains page load performance and security. According to a report from Uptime Institute (2023), 28% of website outages lasting more than 30 minutes are caused by DNS misconfiguration or update errors.

Here are the main reasons for regular monitoring:

  • Domain name retrieval error detected due to incorrect A/AAAA record
  • Avoid DNS abuse used as a DDoS attack vector
  • Ensure TTL time is optimized for page load speed

Recommended periodic check schedule

Regular updates help respond quickly to changes in server IP, hosting, or related service records. Some organizations perform weekly checks, but most SMEs should set up a 2-week cycle higher reliability.

Quickly check the following items:

Item to checkRecommended cycle
A/AAAA record2 weeks
MX record (email)1 month
TXT record (SPF, DKIM)1 month
Reverse DNS2 months

Notes when updating incorrect DNS configuration

Careless DNS editing can cause temporary disconnection. For example: A small business accidentally deleted the MX record during editing, causing internal email disruption for over 14 hours—even though it only took 1 minute to fix after discovery.

Tip: Always back up DNS configuration before editing and use tools like DNSMap or DNSCheck to verify after making changes.

Periodic DNS monitoring checklist

  • ✅ Check IP match in A record
  • ✅ Ensure CNAME does not create a loop
  • ✅ Review TTL time according to access level
  • ✅ Verify DKIM, SPF signatures for no errors
  • ✅ Record changes and reconciliation logs

Brief takeaway

Monitoring and adjusting DNS at the right frequency helps the website operate stably, avoiding service interruptions due to configuration errors. Consider DNS not only as a technical factor but also as “potential bottleneck” affecting the entire digital system of the business.
Quick DNS backup and recovery strategy in case of incidents ensures website sustainability

Backup and rapid DNS recovery strategy to ensure website sustainability in case of incidents

DNS contingency plan: Why is it important?

Loss of connection due to DNS issues can cause website disruption from a few minutes to several hours – directly affecting revenue and reputation. According to the Uptime Institute 2023 report, 60% of businesses lose over 100,000 USD for each hour of downtime.

Below are the negative impacts if there is no DNS recovery strategy:

– Loss of customers due to inaccessible website
– Temporary SEO ranking drop if crawls continuously return errors
– Disruption of email, API, subdomain services

TIP: Applying a multi-provider DNS model can improve recovery capability by 3 times compared to using only one provider.

Configuration checklist for effective DNS backup and recovery

Take the following steps to protect your website when DNS issues occur:

  • Settings 2 parallel DNS systems: For example, use Cloudflare combined with Amazon Route 53
  • Automation backup DNS configuration weekly (via API or manual export)
  • Configure short TTL (from 60-300 seconds) to reduce latency when switching to backup DNS
  • Quarterly simulated DNS disaster recovery test
  • Set up alert monitoring via Pingdom, StatusCake, or UptimeRobot

Real-world examples of DNS incidents & handling methods

In July 2022, an online retail business in Vietnam experienced a DNS incident due to an SOA configuration error, causing the website to be down for 1 hour. Thanks to a pre-connected secondary DNS at DigitalOcean, they recovered service after 5 minutes – minimizing predicted losses from 30 million VND to less than 2 million VND.

Quick comparison table of primary DNS & backup DNS

CriteriaPrimary DNSBackup DNS
Response speed20-50ms30-70ms
Uptime level99.99%99.9%
Automatic activation capabilityNoYes (if health check is configured)

Risk warning when there is no DNS backup solution

– DNS data modified or overwritten due to permission vulnerabilities
– DNS hit by DDoS causing the entire website system to crash completely
– DNS resolver returns no results – response time can extend > 10 seconds

Without preparation, even minor DNS errors can cause significant losses.

Takeaway summary

Website sustainability starts with the ability to recover the DNS system. Establishing a professional backup and redundant DNS system will help businesses operate stably, avoid major damage, and maintain a smooth user experience even during incidents. - DPS.MEDIA JSC -

Your past journey

Proper DNS configuration helps improve page load speed and enhance website security. This is a foundational factor for user experience and SEO performance.

Check your current DNS configuration today. Apply the shared principles to optimize your website more effectively.

You can also learn more about how to choose the right CDN or techniques to mitigate DDoS attacks. These topics contribute to a comprehensive website security strategy.

DPS.MEDIA is always ready to accompany SMEs to optimize digital infrastructure. Don't hesitate to share your thoughts or ask questions by commenting below!

DPS.MEDIA