taalus.com - dns.ninja
taalus.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| NS | ns1.afternic.com ⭐ | ||||||
| A | 2603:5:2126::45🇺🇸 GODADDY-DNS2603:5:2120::/44 | ||||||
| PTR | ns1.afternic.com | ||||||
| A | 97.74.98.69🇺🇸 GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns1.afternic.com | ||||||
| NS | ns2.afternic.com | ||||||
| A | 2603:5:2226::45🇺🇸 GODADDY-DNS2603:5:2220::/44 | ||||||
| PTR | ns2.afternic.com | ||||||
| A | 173.201.66.69🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns2.afternic.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1.afternic.comdns@jomax.net serial=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=1783188441 | ||||||
Same first word
taalus.com |
Similar names
DNS History
12 records (4 active, 8 former)
○NSdns01.msghub.com2015-08-22 → 2017-12-03 · 8 obs
○ 2015-10-18 16:07:18
● 2015-12-18 20:58:50
● 2016-06-19 13:48:18
○ 2016-12-06 08:18:06
● 2017-12-03 11:02:12
○ 2026-02-19 05:58:30
○ 2026-07-04 18:14:08
○NSdns02.msghub.com2015-08-22 → 2016-12-06 · 7 obs
● 2015-10-18 16:07:18
○ 2015-12-18 20:58:50
○ 2016-06-19 13:48:18
● 2016-12-06 08:18:06
○ 2017-12-03 11:02:12
○ 2026-07-04 18:14:08
●NSns1.afternic.com2026-02-19 → 2026-07-04 · 3 obs
● 2026-02-19 05:58:30
● 2026-07-04 18:14:08
○NSns1.msghub.com2015-08-22 → 2017-12-03 · 4 obs
● 2017-12-03 11:02:12
○ 2026-02-19 05:58:30
○ 2026-07-04 18:14:08
●NSns2.afternic.com2026-02-19 → 2026-07-04 · 3 obs
● 2026-02-19 05:58:30
● 2026-07-04 18:14:08
○NSns2.msghub.com2015-08-22 → 2017-12-03 · 4 obs
● 2017-12-03 11:02:12
○ 2026-02-19 05:58:30
○ 2026-07-04 18:14:08
○MX.2026-02-19 → 2026-07-04 · 2 obs
○ 2026-07-04 18:14:08
○MXmx1.e-knowasp.com2015-08-22 → 2017-12-03 · 4 obs
● 2017-12-03 11:02:12
○ 2026-02-19 05:58:30
○ 2026-07-04 18:14:08
○MXmx2.e-knowasp.com2015-08-22 → 2017-12-03 · 4 obs
● 2017-12-03 11:02:12
○ 2026-02-19 05:58:30
○ 2026-07-04 18:14:08
●A13.248.169.482026-02-19 → 2026-07-04 · 3 obs
● 2026-02-19 05:58:30
● 2026-07-04 18:14:08
●A76.223.54.1462026-02-19 → 2026-07-04 · 3 obs
● 2026-02-19 05:58:30
● 2026-07-04 18:14:08
○A77.93.139.2152015-08-22 → 2017-12-03 · 4 obs
● 2017-12-03 11:02:12
○ 2026-02-19 05:58:30
○ 2026-07-04 18:14:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| taalus.com | ns1.afternic.com, ns2.afternic.com | 4 records |
✅ Authoritative Response
Server:173.201.66.69
NS records: ns1.afternic.com, ns2.afternic.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for taalus.com (unsigned zone)
⏱️ Timing
Total: 148ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 76.223.54.146, 13.248.169.48 |
| NS | 2 | ns1.afternic.com, ns2.afternic.com |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns2.afternic.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)
Analysis
IP Addresses
taalus.com points to the IP addresses 13.248.169.48 and 76.223.54.146
Two other host names, along with pt10.com, 6461796c6967687477696e64796a616e6540686f746d616message.niftymed.com and zdse.xyz, also share IP numbers with taalus.com.
Name Servers
The NS records for taalus.com delegate to ns1.afternic.com and ns2.afternic.com.
taalus.com shares its NS records with other domains, for example host-203-133-52-10.static.kbtelecom.net, pity(0x6675636b).com, archonomy.com and two others.
There is at least partial name server overlap between taalus.com and other domains — rhine.co, easyrun.us, gmsfx.com and two more among them.
These name servers tend to appear in combination with the name servers verification-m3erh32ujyoastvophjvuz.ns101.verify.hn, verification-d3jclucsp89ganyqbydeny.ns101.verify.hn, verification-vesbet7nkettdw2mc9cgox.ns101.verify.hn and verification-lddnswq5f7fujuwt34eydq.ns101.verify.hn.
ns1.afternic.com resolves to 97.74.98.69 and 2603:5:2126::45. Likewise, ns2.afternic.com resolves to 173.201.66.69 and 2603:5:2226::45 — two IP addresses apiece.