DNS Records for
lyricslk.com
🐛 Hunting for rogue glue records.
DNS Records forlyricslk.com
Domain DNS Health Score
90%
Total Tests
29
Passed
26
Critical Issues
1
First-Visit DNS
~35ms
Excellent
Returning Visit
~0ms
Fully cached
CNAME Depth
None
Direct A record
TTL Strategy
Balanced
TTL values are well-balanced across record types
DNS Provider
Cloudflare
Global Anycast
Avg NS Response
4ms
Fast
Insights
A2
AAAA2
NS2
MX1
TXT1
SPFok
DMARCwarn
DNSSECinfo
CAAinfo
93%
40/43 tests
TTL cache lifetime
1m
5m
30m
1h
4h
1d
2d
7d
A
Good for CDN or dynamic setups (5 min). Balances freshness with caching.5 min
AAAA
Good for CDN or dynamic setups (5 min). Balances freshness with caching.5 min
NS
13h 34m — appropriate for nameserver records.13.6 hr
MX
5 min — appropriate for mail server records.5 min
SOA
30 min
TXT
5 min — appropriate for TXT records.5 min
Resolution waterfall
First visit ~35msReturning ~0ms
Root → TLD nameserver
5ms
TLD → Authoritative NS
20ms
NS → A record (apex)
15ms
NS → AAAA record (IPv6)
15ms
Benchmark: excellent
Per-nameserver response time
avg 4msspread 0ms
duke.ns.cloudflare.com
4ms
tina.ns.cloudflare.com
4ms
Provider Cloudflare Anycast confirmed
www resolution
www.lyricslk.comDirect A record — no CNAME chain
172.67.160.129104.21.9.138SOA timing
Serial
2400507161Refresh
2.8 hr
How often secondaries re-check
Retry
40 min
Wait after a failed refresh
Expire
7 days
Secondaries stop serving after
Min TTL
30 min
Negative cache duration
Zone last updated
Serial format isn't YYYYMMDDnn — age can't be inferred.
Negative cache
NXDOMAIN responses are cached for 30 min. Typos against this zone stick around that long.
Glue records at parent
via f.gtld-servers.net
| Nameserver | IPv4 | IPv6 | Zone match |
|---|---|---|---|
| duke.ns.cloudflare.com | 108.162.193.110, 172.64.33.110, 173.245.59.110 | 2606:4700:58::adf5:3b6e, 2803:f800:50::6ca2:c16e, 2a06:98c1:50::ac40:216e | match |
| tina.ns.cloudflare.com | 108.162.192.230, 172.64.32.230, 173.245.58.230 | 2606:4700:50::adf5:3ae6, 2803:f800:50::6ca2:c0e6, 2a06:98c1:50::ac40:20e6 | match |
Mail exchange priority
1 MX record
pref 0
_dc-mx.216e416b2f07.lyricslk.com
Primary
Only one MX record — no failover path if this server is unreachable.
SPF mechanism chain
v=spf1
ip4:67.43.13.32IPv4 range allowed
aSenders matching domain's A
mxSenders matching domain's MX
ip4:50.116.75.183IPv4 range allowed
~allsoftfail
These nameservers are responsible for answering queries about your domain
2 Records
duke.ns.cloudflare.com
tina.ns.cloudflare.com
Cloudflare
Your domain is using Cloudflare's DNS service, which provides DDoS protection, global CDN, and performance optimization features.
Source: This information was kindly provided by f.gtld-servers.net 🙏🏼
Good. f.gtld-servers.net has information for your TLD. This confirms your domain is properly delegated.
Good. The parent server has your nameservers listed and they match the actual NS records. This ensures consistent DNS resolution.
Glue Records from Parent Server
Information provided by f.gtld-servers.net
duke.ns.cloudflare.com
Nameserver
IPv4 Addresses:
108.162.193.110172.64.33.110173.245.59.110IPv6 Addresses:
2606:4700:58::adf5:3b6e2803:f800:50::6ca2:c16e2a06:98c1:50::ac40:216etina.ns.cloudflare.com
Nameserver
IPv4 Addresses:
108.162.192.230172.64.32.230173.245.58.230IPv6 Addresses:
2606:4700:50::adf5:3ae62803:f800:50::6ca2:c0e62a06:98c1:50::ac40:20e6Note:
The parent server is providing glue records for these nameservers. While not required (since the nameservers are not under your domain), this helps optimize DNS resolution.
| Status | Test name | Information |
|---|---|---|
Authoritative Nameservers | These nameservers are responsible for answering queries about your domain 2 Records duke.ns.cloudflare.comtina.ns.cloudflare.comCloudflareYour domain is using Cloudflare's DNS service, which provides DDoS protection, global CDN, and performance optimization features. Source: This information was kindly provided by f.gtld-servers.net 🙏🏼 | |
TLD Delegation Check | Good. f.gtld-servers.net has information for your TLD. This confirms your domain is properly delegated. | |
Nameservers Listed at Parent | Good. The parent server has your nameservers listed and they match the actual NS records. This ensures consistent DNS resolution. | |
Glue Records from Parent | Glue Records from Parent ServerInformation provided by f.gtld-servers.net duke.ns.cloudflare.comNameserver IPv4 Addresses: 108.162.193.110172.64.33.110173.245.59.110IPv6 Addresses: 2606:4700:58::adf5:3b6e2803:f800:50::6ca2:c16e2a06:98c1:50::ac40:216etina.ns.cloudflare.comNameserver IPv4 Addresses: 108.162.192.230172.64.32.230173.245.58.230IPv6 Addresses: 2606:4700:50::adf5:3ae62803:f800:50::6ca2:c0e62a06:98c1:50::ac40:20e6Note: The parent server is providing glue records for these nameservers. While not required (since the nameservers are not under your domain), this helps optimize DNS resolution. |
duke.ns.cloudflare.com
Cloudflare
IPv4 Addresses
108.162.193.110
173.245.59.110
172.64.33.110
IPv6 Addresses
2606:4700:58::adf5:3b6e
2a06:98c1:50::ac40:216e
2803:f800:50::6ca2:c16e
Authoritative
Non-Recursive
TCP
UDP
TTL: 172,800s (2 days)
tina.ns.cloudflare.com
Cloudflare
IPv4 Addresses
108.162.192.230
173.245.58.230
172.64.32.230
IPv6 Addresses
2803:f800:50::6ca2:c0e6
2a06:98c1:50::ac40:20e6
2606:4700:50::adf5:3ae6
Authoritative
Non-Recursive
TCP
UDP
TTL: 172,800s (2 days)
Good. No nameservers allow recursive queries.
Cloudflare’s DNS uses a global network to speed up responses. Normally, the IP addresses at the parent nameservers and Cloudflare’s servers should match. If they don’t, it might just be a short-term update.
Cloudflare manages glue records through their global DNS infrastructure.
Good. The NS records at all your nameservers are identical.
Good. All nameservers listed at the parent server responded.
All NS records appear to be valid hostnames.
You have 2 nameservers. This meets the minimum requirement, though RFC2182 section 5 recommends at least 3 for better reliability.
Good. All nameservers are answering authoritatively for your domain.
Good. All NS records match between parent and nameservers, as required by RFC1034 section 3.6.
Good. All parent-listed nameservers are reported by your nameservers, as required by RFC1034 section 3.6.
Good. No CNAME records found for NS records, as per RFC1912 section 2.4 and RFC2181 section 10.3.
Anycast provider detected (Cloudflare).While 3 IP pair(s) share a
/16
prefix, Cloudflare distributes these across globally diverse datacenters using anycast routing. No subnet diversity concern per RFC2182 section 5.| Status | Test name | Information |
|---|---|---|
Nameserver Records from Zone | duke.ns.cloudflare.comCloudflare IPv4 Addresses 108.162.193.110 173.245.59.110 172.64.33.110 IPv6 Addresses 2606:4700:58::adf5:3b6e 2a06:98c1:50::ac40:216e 2803:f800:50::6ca2:c16e Authoritative Non-Recursive TCP UDP TTL: 172,800s (2 days) tina.ns.cloudflare.comCloudflare IPv4 Addresses 108.162.192.230 173.245.58.230 172.64.32.230 IPv6 Addresses 2803:f800:50::6ca2:c0e6 2a06:98c1:50::ac40:20e6 2606:4700:50::adf5:3ae6 Authoritative Non-Recursive TCP UDP TTL: 172,800s (2 days) | |
Open Recursive Queries | Good. No nameservers allow recursive queries. | |
Glue Record Consistency | Cloudflare’s DNS uses a global network to speed up responses. Normally, the IP addresses at the parent nameservers and Cloudflare’s servers should match. If they don’t, it might just be a short-term update. | |
Missing Glue for NS Records | Cloudflare manages glue records through their global DNS infrastructure. | |
Mismatched NS records | Good. The NS records at all your nameservers are identical. | |
DNS servers responded | Good. All nameservers listed at the parent server responded. | |
Name of nameservers are valid | All NS records appear to be valid hostnames. | |
Nameserver Redundancy Check | You have 2 nameservers. This meets the minimum requirement, though RFC2182 section 5 recommends at least 3 for better reliability. | |
Lame Delegation Check | Good. All nameservers are answering authoritatively for your domain. | |
Parent Missing Nameservers | Good. All NS records match between parent and nameservers, as required by RFC1034 section 3.6. | |
Zone Missing Nameservers | Good. All parent-listed nameservers are reported by your nameservers, as required by RFC1034 section 3.6. | |
CNAMEs at Apex Check | Good. No CNAME records found for NS records, as per RFC1912 section 2.4 and RFC2181 section 10.3. | |
NS IP Subnet Diversity | Anycast provider detected (Cloudflare).While 3 IP pair(s) share a /16 prefix, Cloudflare distributes these across globally diverse datacenters using anycast routing. No subnet diversity concern per RFC2182 section 5. |
Info
Primary Nameserver
duke.ns.cloudflare.com
Hostmaster Email
dns.cloudflare.com
Serial Number
2400507161
Non-Standard (Unix Timestamp)
A unique version number that changes whenever the zone file is updated
Time Intervals
Refresh10000 seconds (2 hours)
How often secondary nameservers check for updates (20m - 24h)
Retry2400 seconds (40 minutes)
How long to wait before retrying a failed zone transfer (2m - 2h)
Expire604800 seconds (7 days)
How long secondary servers serve stale zone data (1w - 4w)
TTL1800 seconds (30 minutes)
Default time-to-live for resource records (5m - 24h)
SOA Serial numbers per nameserver:
duke.ns.cloudflare.com: 2400507161
tina.ns.cloudflare.com: 2400507161
Good. All nameservers report the same SOA serial number.
Pass
OK. duke.ns.cloudflare.com is correctly listed as one of your nameservers.
Info
Your SOA serial number is: 2400507161. Using Cloudflare's automatic serial number management.
Pass
OK. Your SOA REFRESH interval is: 10000 seconds (167 minutes). This is within the recommended range of 1200-43200 seconds as per RFC1912 section 2.2.
Pass
OK. Your SOA RETRY value is: 2400 seconds (40 minutes). This is within the recommended range of 120-7200 seconds as per RFC1912 section 2.2.
Info
Current expire time is 604800 seconds (7 days). Using Cloudflare's optimized SOA expire time.
Pass
OK. Your SOA MINIMUM TTL is: 1800 seconds (30 minutes). This value is used for negative caching and is within the recommended range of 180-86400 seconds as per RFC2308 section 4.
| Status | Test name | Information |
|---|---|---|
SOA record | Primary Nameserverduke.ns.cloudflare.com Hostmaster Emaildns.cloudflare.com Serial Number 2400507161 Non-Standard (Unix Timestamp) A unique version number that changes whenever the zone file is updated Time IntervalsRefresh10000 seconds (2 hours) How often secondary nameservers check for updates (20m - 24h) Retry2400 seconds (40 minutes) How long to wait before retrying a failed zone transfer (2m - 2h) Expire604800 seconds (7 days) How long secondary servers serve stale zone data (1w - 4w) TTL1800 seconds (30 minutes) Default time-to-live for resource records (5m - 24h) | |
SOA Serial Consistency | SOA Serial numbers per nameserver:
duke.ns.cloudflare.com: 2400507161
tina.ns.cloudflare.com: 2400507161
Good. All nameservers report the same SOA serial number. | |
SOA MNAME entry | OK. duke.ns.cloudflare.com is correctly listed as one of your nameservers. | |
SOA Serial | Your SOA serial number is: 2400507161. Using Cloudflare's automatic serial number management. | |
SOA REFRESH | OK. Your SOA REFRESH interval is: 10000 seconds (167 minutes). This is within the recommended range of 1200-43200 seconds as per RFC1912 section 2.2. | |
SOA RETRY | OK. Your SOA RETRY value is: 2400 seconds (40 minutes). This is within the recommended range of 120-7200 seconds as per RFC1912 section 2.2. | |
SOA EXPIRE | Current expire time is 604800 seconds (7 days). Using Cloudflare's optimized SOA expire time. | |
SOA MINIMUM TTL | OK. Your SOA MINIMUM TTL is: 1800 seconds (30 minutes). This value is used for negative caching and is within the recommended range of 180-86400 seconds as per RFC2308 section 4. |
IPv4 Configuration
Your domain is using Cloudflare's infrastructure for content delivery and security
IPv4 Addresses
104.21.9.138172.67.160.129Configuration Benefits
Global content delivery
Content served from edge locations worldwide
DDoS protection
Built-in protection against distributed denial-of-service attacks
Load balancing
Intelligent traffic distribution across global network
Automatic failover
Seamless switching to healthy servers during outages
TTL: 300s
Provides a good balance between propagation speed and DNS loadPass
TTL of 300 seconds provides a good balance between propagation speed and DNS load.
| Status | Test name | Information |
|---|---|---|
A Record Configuration | IPv4 ConfigurationYour domain is using Cloudflare's infrastructure for content delivery and security IPv4 Addresses 104.21.9.138172.67.160.129Configuration Benefits Global content delivery Content served from edge locations worldwide DDoS protection Built-in protection against distributed denial-of-service attacks Load balancing Intelligent traffic distribution across global network Automatic failover Seamless switching to healthy servers during outages TTL: 300s Provides a good balance between propagation speed and DNS load | |
A Record TTL | TTL of 300 seconds provides a good balance between propagation speed and DNS load. |
IPv6 Configuration
Your domain is using Cloudflare's infrastructure for content delivery and security
IPv6 Addresses
2606:4700:3032::ac43:a0812606:4700:3030::6815:98aTTL: 300s
Provides a good balance between propagation speed and DNS load| Status | Test name | Information |
|---|---|---|
IPv6 Configuration | IPv6 ConfigurationYour domain is using Cloudflare's infrastructure for content delivery and security IPv6 Addresses 2606:4700:3032::ac43:a0812606:4700:3030::6815:98aTTL: 300s Provides a good balance between propagation speed and DNS load |
All nameservers are reporting the same mail server configuration. This consistency ensures reliable email delivery.
Current mail exchanger (MX) configuration:
0 _dc-mx.216e416b2f07.lyricslk.com 67.43.13.32 (No Glue)
These records define the servers responsible for receiving email for your domain.
Error: The following mail server hostnames contain invalid characters:
_dc-mx.216e416b2f07.lyricslk.com
All mail servers use public IP addresses, ensuring global email delivery.
Pass
Mail servers are properly configured without CNAME records.
Pass
Each mail server has unique IP addresses, indicating proper distribution of mail handling.
Warning
Warning: The following mail servers have IPs missing reverse DNS (PTR) records:
_dc-mx.216e416b2f07.lyricslk.com: 67.43.13.32
This may affect email deliverability.
| Status | Test name | Information |
|---|---|---|
Mail Server Consistency | All nameservers are reporting the same mail server configuration. This consistency ensures reliable email delivery. | |
Mail Server Configuration | Current mail exchanger (MX) configuration:
0 _dc-mx.216e416b2f07.lyricslk.com 67.43.13.32 (No Glue)
These records define the servers responsible for receiving email for your domain. | |
Mail Server Hostname Validation | Error: The following mail server hostnames contain invalid characters:
_dc-mx.216e416b2f07.lyricslk.com | |
Public IP Validation | All mail servers use public IP addresses, ensuring global email delivery. | |
CNAME Validation | Mail servers are properly configured without CNAME records. | |
IP Uniqueness | Each mail server has unique IP addresses, indicating proper distribution of mail handling. | |
Reverse DNS Records | Warning: The following mail servers have IPs missing reverse DNS (PTR) records:
_dc-mx.216e416b2f07.lyricslk.com: 67.43.13.32
This may affect email deliverability. |
WWW record type: CDN Proxied (Proxied through Cloudflare)
www.
CDN Proxied Record
IPv4 Addresses
172.67.160.129104.21.9.138IPv6 Addresses
2606:4700:3030::6815:98a2606:4700:3032::ac43:a081CDN Configuration
Your WWW record is proxied through Cloudflare, providing:
- Automatic CDN integration and caching
- DDoS protection and security features
- Load balancing and failover capabilities
- Easy infrastructure changes through the provider dashboard
| Status | Test name | Information |
|---|---|---|
WWW Configuration | WWW record type: CDN Proxied (Proxied through Cloudflare) www. CDN Proxied Record IPv4 Addresses 172.67.160.129104.21.9.138IPv6 Addresses 2606:4700:3030::6815:98a2606:4700:3032::ac43:a081CDN Configuration Your WWW record is proxied through Cloudflare, providing:
|
Info
This domain uses Cloudflare. DNSSEC queries returned SERVFAIL, which may be due to resolver compatibility rather than a configuration issue. Cloudflare manages DNSSEC through their infrastructure — check their dashboard for DNSSEC status.
Info
Your domain uses Cloudflare nameservers. Zone transfers are managed securely through Cloudflare's infrastructure using proprietary protocols.
Learn more: https://dnschkr.com/blog/dns-attacks-guide#dns-zone-transfer-attack-axfr
Info
No CAA records found. While optional, CAA records help control which Certificate Authorities can issue certificates for your domain.
Checked 8 common subdomains. Found 1 CNAME record — all targets resolve correctly. No dangling CNAME risk detected.
Learn more: https://dnschkr.com/blog/dns-attacks-guide#subdomain-takeover
| Status | Test name | Information |
|---|---|---|
DNSSEC | This domain uses Cloudflare. DNSSEC queries returned SERVFAIL, which may be due to resolver compatibility rather than a configuration issue. Cloudflare manages DNSSEC through their infrastructure — check their dashboard for DNSSEC status. | |
Zone Transfer | Your domain uses Cloudflare nameservers. Zone transfers are managed securely through Cloudflare's infrastructure using proprietary protocols.
Learn more: https://dnschkr.com/blog/dns-attacks-guide#dns-zone-transfer-attack-axfr | |
CAA Records | No CAA records found. While optional, CAA records help control which Certificate Authorities can issue certificates for your domain. | |
Subdomain Takeover | Checked 8 common subdomains. Found 1 CNAME record — all targets resolve correctly. No dangling CNAME risk detected.
Learn more: https://dnschkr.com/blog/dns-attacks-guide#subdomain-takeover |
Info
Click any row to copy the raw value
v | spf1 ip4:67.43.13.32 +a +mx +ip4:50.116.75.183 ~all |
Showing 1 of 1 record
Pass
Found SPF record: v=spf1 ip4:67.43.13.32 +a +mx +ip4:50.116.75.183 ~all
Warning
No DMARC record found. DMARC helps prevent email spoofing and provides reporting capabilities. Consider adding a DMARC record to improve email security.
| Status | Test name | Information | ||||
|---|---|---|---|---|---|---|
TXT Records | Click any row to copy the raw value
Showing 1 of 1 record | |||||
SPF Record | Found SPF record: v=spf1 ip4:67.43.13.32 +a +mx +ip4:50.116.75.183 ~all | |||||
DMARC Record | No DMARC record found. DMARC helps prevent email spoofing and provides reporting capabilities. Consider adding a DMARC record to improve email security. |