buzzfeedly.com - robtex.com
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=1771291435 | ||||||
Same first word
buzzfeedly.com |
DNS History
15 records (3 active, 12 former)
●NSa.nsvauban.net2026-02-24 → 2026-02-25 · 3 obs
○ 2018-01-18 17:22:02
● 2026-02-24 05:46:38
● 2026-02-25 11:21:20
● 2026-02-24 05:46:38
● 2026-02-25 11:21:20
●NSb.nsvauban.net2026-02-24 → 2026-02-25 · 3 obs
○ 2018-01-18 17:22:02
● 2026-02-24 05:46:38
● 2026-02-25 11:21:20
● 2026-02-24 05:46:38
● 2026-02-25 11:21:20
○NSdns1.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○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-02-25 11:21:20
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○NSdns2.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○NSdns3.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○NSdns4.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○NSdns5.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○MXeforward1.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○MXeforward2.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○MXeforward3.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○MXeforward4.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○MXeforward5.registrar-servers.com2017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
●A160.16.116.1182026-02-24 → 2026-02-25 · 3 obs
○ 2018-01-18 17:22:02
● 2026-02-24 05:46:38
● 2026-02-25 11:21:20
● 2026-02-24 05:46:38
● 2026-02-25 11:21:20
○A192.64.119.782017-01-04 → 2017-01-04 · 3 obs
● 2017-01-04 22:22:34
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
○ 2018-01-18 17:22:02
○ 2026-02-25 11:21:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, l.gtld-servers.net, j.gtld-servers.net, d.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: 1784ms | 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 |
AI analysis
buzzfeedly.com points to IP number 160.16.116.118.
Other host names, for instance, limcom.org share IP numbers with buzzfeedly.com.
buzzfeedly.com is delegated to two name servers: a.nsvauban.net and b.nsvauban.net.
buzzfeedly.com uses the same name server setup as other domains such as pulsakita.biz, travelclothes.org, besteapps.info, myessp.com and city-education.org.
Host names with one IP number:
a.nsvauban.net points to: 133.167.99.88.
b.nsvauban.net points to: 49.212.202.62.