buzzfeedly.com - dns.ninja
buzzfeedly.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 160.16.116.118🇯🇵 SAKURA-B160.16.0.0/17 SAKURA Internet // EAST JAPAN BACKBONE Sakaisuji Honmachi Bldg. 9F 1-8-14 Minami-Honmachi, Chuo-ku Osaka 541-0054, Japan | ||||||
| PTR | tk2-234-26614.vs.sakura.ne.jp | ||||||
| NS | a.nsvauban.net ⭐ | ||||||
| A | 133.167.99.88🇯🇵 SAKURA-C133.167.0.0/16 (OSAKA) SAKURA Internet // WEST JAPAN BACKBONE Grand Front Osaka Tower A 35F, 4-20 Ofukacho, Kita-ku, Osaka, Osaka 530-0011, Japan | ||||||
| PTR | os3-379-22834.vs.sakura.ne.jp | ||||||
| NS | b.nsvauban.net | ||||||
| A | 49.212.202.62🇯🇵 SAKURA-C49.212.0.0/16 (7/OSAKA) SAKURA Internet // WEST JAPAN BACKBONE 1-8-15 Kyutaro-cho, Chuo Osaka 541-0056, Japan | ||||||
| PTR | os3-306-42558.vs.sakura.ne.jp | ||||||
| SOA | a.nsvauban.netadmin@buzzfeedly.com 2025-08-05 #3 | ||||||
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=1783837322 | ||||||
Same first word
buzzfeedly.com |
DNS History
15 records (3 active, 12 former)
●NSa.nsvauban.net2026-02-24 → 2026-07-12 · 3 obs
○ 2018-01-18 17:22:02
● 2026-02-24 05:46:38
● 2026-07-12 06:42:00
● 2026-02-24 05:46:38
● 2026-07-12 06:42:00
●NSb.nsvauban.net2026-02-24 → 2026-07-12 · 3 obs
○ 2018-01-18 17:22:02
● 2026-02-24 05:46:38
● 2026-07-12 06:42:00
● 2026-02-24 05:46:38
● 2026-07-12 06:42:00
○NSdns1.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○NSdns1.registrar-servers.com,2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○NSdns2.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○NSdns3.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○NSdns4.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○NSdns5.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○MXeforward1.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○MXeforward2.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○MXeforward3.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○MXeforward4.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○MXeforward5.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
●A160.16.116.1182026-02-24 → 2026-07-12 · 3 obs
○ 2018-01-18 17:22:02
● 2026-02-24 05:46:38
● 2026-07-12 06:42:00
● 2026-02-24 05:46:38
● 2026-07-12 06:42:00
○A192.64.119.782017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
○ 2018-01-18 17:22:02
○ 2026-07-12 06:42:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, k.gtld-servers.net, a.gtld-servers.net, m.gtld-servers.net... | - |
| buzzfeedly.com | a.nsvauban.net, b.nsvauban.net | - |
✅ Authoritative Response
Server:133.167.99.88
NS records: a.nsvauban.net, b.nsvauban.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for buzzfeedly.com (unsigned zone)
⏱️ Timing
Total: 885ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 160.16.116.118 |
| NS | 2 | a.nsvauban.net, b.nsvauban.net |
| SOA | 1 | a.nsvauban.net admin.buzzfeedly.com |
Analysis
IP Addresses
buzzfeedly.com resolves to one IP address: 160.16.116.118.
Among the host names that share IP numbers with buzzfeedly.com is limcom.org, as one example.
Name Servers
The NS records for buzzfeedly.com delegate to a.nsvauban.net and b.nsvauban.net.
buzzfeedly.com uses the same name servers as several other domains — among them pulsakita.biz, travelclothes.org, montrealdating.info and two more.
Both a.nsvauban.net and b.nsvauban.net have a single IP address each — a.nsvauban.net resolves to 133.167.99.88 while b.nsvauban.net resolves to 49.212.202.62.