verifyauth.com - dns.ninja
verifyauth.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.atom.com ⭐ | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| TXT | f0095018235b8109a2bf9f65674a1784b6971ed6 | ||||||
| SOA | ns1.atom.comhostmaster@verifyauth.com 2025-08-24 #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.netnstld@verisign-grs.com serial=1783217966 | ||||||
Same first word
verifyauth.com |
Similar names
authverify.com |
authverify.at |
authverify.online |
authverify.duckdns.org |
authverify.blogspot.com |
authverify.blogspot.in |
DNS History
10 records (3 active, 7 former)
○NSdns1.registrar-servers.com2018-08-24 → 2018-08-29 · 4 obs
● 2018-08-29 14:30:22
○ 2026-03-31 00:10:32
○ 2026-07-05 02:38:42
○NSdns2.registrar-servers.com2018-08-24 → 2018-08-29 · 4 obs
● 2018-08-29 14:30:22
○ 2026-03-31 00:10:32
○ 2026-07-05 02:38:42
●NSns1.atom.com2026-03-31 → 2026-07-05 · 3 obs
● 2026-03-31 00:10:32
● 2026-07-05 02:38:42
●NSns2.atom.com2026-03-31 → 2026-07-05 · 3 obs
● 2026-03-31 00:10:32
● 2026-07-05 02:38:42
○MXeforward1.registrar-servers.com2018-08-24 → 2018-08-29 · 4 obs
● 2018-08-29 14:30:22
○ 2026-03-31 00:10:32
○ 2026-07-05 02:38:42
○MXeforward2.registrar-servers.com2018-08-24 → 2018-08-29 · 4 obs
● 2018-08-29 14:30:22
○ 2026-03-31 00:10:32
○ 2026-07-05 02:38:42
○MXeforward3.registrar-servers.com2018-08-24 → 2018-08-29 · 4 obs
● 2018-08-29 14:30:22
○ 2026-03-31 00:10:32
○ 2026-07-05 02:38:42
○MXeforward4.registrar-servers.com2018-08-24 → 2018-08-29 · 4 obs
● 2018-08-29 14:30:22
○ 2026-03-31 00:10:32
○ 2026-07-05 02:38:42
○MXeforward5.registrar-servers.com2018-08-24 → 2018-08-29 · 4 obs
● 2018-08-29 14:30:22
○ 2026-03-31 00:10:32
○ 2026-07-05 02:38:42
●A52.20.84.622026-03-31 → 2026-07-05 · 2 obs
● 2026-07-05 02:38:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, j.gtld-servers.net, m.gtld-servers.net, l.gtld-servers.net... | - |
| verifyauth.com | ns1.atom.com, ns2.atom.com | 2 records |
✅ Authoritative Response
Server:44.219.81.145
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for verifyauth.com (unsigned zone)
⏱️ Timing
Total: 3110ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns2.atom.com, ns1.atom.com |
| TXT | 1 | f0095018235b8109a2bf9f65674a1784b6971ed6 |
| SOA | 1 | ns1.atom.com hostmaster.verifyauth.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
verifyauth.com has exactly one IP address — 52.20.84.62.
ibujo.com, trademap.com, www.broadbound.com plus two other host names have IP numbers in common with verifyauth.com.
Name Servers
The NS records for verifyauth.com delegate to ns1.atom.com and ns2.atom.com.
The name server configuration of verifyauth.com is shared with other domains, for instance nutrisma.com, azrion.com, geomba.com and two others.
verifyauth.com shares at least some of its name servers with domains including dyggo.com, hathar.com and cryptec.org
These name servers often co-occur with the name servers verification-hifl3q92x5aexed9ijgct6.ns101.verify.hn.
ns1.atom.com resolves to 44.219.81.145. ns2.atom.com resolves to 50.19.240.86. Both host names point to a single IP number.