api.labnify.com - dns.ninja
api.labnify.com
| DNSSEC | ⚠️ Not signed | ||||||
| MX | api.labnify.com ⭐ | ||||||
| MX | mx.byte.labnify.com ⭐ | ||||||
| TXT | v=spf1 a mx ptr a:bp.labnify.com ip4:178.16.55.103/24 include:spf.byte.labnif... | ||||||
labnify.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2606:4700:3030::6815:5e8f🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US ✓ In HTTPS hints | ||||||
| A | 2606:4700:3030::ac43:88db🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US ✓ In HTTPS hints | ||||||
| A | 104.21.94.143Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US ✓ In HTTPS hints | ||||||
| A | 172.67.136.219🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US ✓ In HTTPS hints | ||||||
| NS | alex.ns.cloudflare.com ⭐ | ||||||
| NS | elinore.ns.cloudflare.com | ||||||
| MX | mx.yandex.net ⭐ | ||||||
| MX | mx.byte.labnify.com(50) | ||||||
| TXT | cryptomus=a8e1901c | ||||||
| TXT | google-site-verification=1BIIK8XWI96kbtTqOxwkXJ_iqPTXNoTLOkGvJU5DjBw | ||||||
| TXT | v=spf1 a mx include:amazonses.com include:_spf.elasticemail.com include:_spf.... | ||||||
| TXT | yandex-verification: 4a4be39aa69d0ce4 | ||||||
| HTTPS | HTTP/3, HTTP/2 ✓ hints match | ||||||
| IPv4 hints | 104.21.94.143, 172.67.136.219 | ||||||
| IPv6 hints | 2606:4700:3030::6815:5e8f, 2606:4700:3030::ac43:88db | ||||||
| ECH | X25519, HKDF-SHA256 + AES-128-GCM draft, id=217, name=cloudflare-ech.com | ||||||
| SOA | alex.ns.cloudflare.comdns@cloudflare.com serial=2410370651 | ||||||
MX for
api.labnify.com |
Same first word
Similar names
DNS History
2 records (2 active, 0 former)
●MXapi.labnify.com2026-03-10 → 2026-07-29 · 2 obs
● 2026-03-10 10:24:56
● 2026-07-29 06:29:00
● 2026-07-29 06:29:00
●MXmx.byte.labnify.com2026-03-10 → 2026-07-29 · 2 obs
● 2026-03-10 10:24:56
● 2026-07-29 06:29:00
● 2026-07-29 06:29:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| labnify.com | alex.ns.cloudflare.com, elinore.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.193.100
NS records: alex.ns.cloudflare.com, elinore.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for labnify.com (unsigned zone)
⏱️ Timing
Total: 157ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| MX | 2 | api.labnify.com (pri: 10), mx.byte.labnify.com (pri: 10) |
| TXT | 1 | v=spf1 a mx ptr a:bp.labnify.com ip4:178 |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (alex.ns.cloudflare.com, alex.ns.cloudflare.com, alex.ns.cloudflare.com...)
Analysis
Mail Server Role
api.labnify.com acts as its own mail server.
mx.byte.labnify.com frequently appears as a mail server alongside api.labnify.com.
Mail Servers
api.labnify.com is handled by two mail servers: api.labnify.com and mx.byte.labnify.com.
api.labnify.com shares at least some of its mail servers with other domains, such as labnify.com and byte.labnify.com.
These mail servers are frequently seen alongside the mail servers mx.yandex.net.