DNS Records for
sweetjames.com
🐛 Hunting for rogue glue records.
DNS Records forsweetjames.com
Domain DNS Health Score
100%
Total Tests
28
Passed
28
Critical Issues
0
First-Visit DNS
~50ms
Good
Returning Visit
~0ms
Fully cached
CNAME Depth
1 hop
Optimal
TTL Strategy
Balanced
TTL values are well-balanced across record types
DNS Provider
Cloudflare
Global Anycast
Avg NS Response
2ms
Fast
These nameservers are responsible for answering queries about your domain
2 Records
ophelia.ns.cloudflare.com
maxim.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 k.gtld-servers.net 🙏🏼
Good. k.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 k.gtld-servers.net
ophelia.ns.cloudflare.com
Nameserver
IPv4 Addresses:
108.162.194.248162.159.38.248172.64.34.248IPv6 Addresses:
2606:4700:50::a29f:26f82803:f800:50::6ca2:c2f82a06:98c1:50::ac40:22f8maxim.ns.cloudflare.com
Nameserver
IPv4 Addresses:
108.162.195.198162.159.44.198172.64.35.198IPv6 Addresses:
2606:4700:58::a29f:2cc62803:f800:50::6ca2:c3c62a06:98c1:50::ac40:23c6Note:
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 ophelia.ns.cloudflare.commaxim.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 k.gtld-servers.net 🙏🏼 | |
TLD Delegation Check | Good. k.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 k.gtld-servers.net ophelia.ns.cloudflare.comNameserver IPv4 Addresses: 108.162.194.248162.159.38.248172.64.34.248IPv6 Addresses: 2606:4700:50::a29f:26f82803:f800:50::6ca2:c2f82a06:98c1:50::ac40:22f8maxim.ns.cloudflare.comNameserver IPv4 Addresses: 108.162.195.198162.159.44.198172.64.35.198IPv6 Addresses: 2606:4700:58::a29f:2cc62803:f800:50::6ca2:c3c62a06:98c1:50::ac40:23c6Note: 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. |
maxim.ns.cloudflare.com
Cloudflare
IPv4 Addresses
108.162.195.198
172.64.35.198
162.159.44.198
IPv6 Addresses
2a06:98c1:50::ac40:23c6
2803:f800:50::6ca2:c3c6
2606:4700:58::a29f:2cc6
Authoritative
Non-Recursive
TCP
UDP
TTL: 172,800s (2 days)
ophelia.ns.cloudflare.com
Cloudflare
IPv4 Addresses
108.162.194.248
172.64.34.248
162.159.38.248
IPv6 Addresses
2606:4700:50::a29f:26f8
2803:f800:50::6ca2:c2f8
2a06:98c1:50::ac40:22f8
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 | maxim.ns.cloudflare.comCloudflare IPv4 Addresses 108.162.195.198 172.64.35.198 162.159.44.198 IPv6 Addresses 2a06:98c1:50::ac40:23c6 2803:f800:50::6ca2:c3c6 2606:4700:58::a29f:2cc6 Authoritative Non-Recursive TCP UDP TTL: 172,800s (2 days) ophelia.ns.cloudflare.comCloudflare IPv4 Addresses 108.162.194.248 172.64.34.248 162.159.38.248 IPv6 Addresses 2606:4700:50::a29f:26f8 2803:f800:50::6ca2:c2f8 2a06:98c1:50::ac40:22f8 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
maxim.ns.cloudflare.com
Hostmaster Email
dns.cloudflare.com
Serial Number
2400655214
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:
maxim.ns.cloudflare.com: 2400655214
ophelia.ns.cloudflare.com: 2400655214
Good. All nameservers report the same SOA serial number.
Pass
OK. maxim.ns.cloudflare.com is correctly listed as one of your nameservers.
Info
Your SOA serial number is: 2400655214. 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 Nameservermaxim.ns.cloudflare.com Hostmaster Emaildns.cloudflare.com Serial Number 2400655214 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:
maxim.ns.cloudflare.com: 2400655214
ophelia.ns.cloudflare.com: 2400655214
Good. All nameservers report the same SOA serial number. | |
SOA MNAME entry | OK. maxim.ns.cloudflare.com is correctly listed as one of your nameservers. | |
SOA Serial | Your SOA serial number is: 2400655214. 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
Single IPv4 address configuration
IPv4 Addresses
162.159.134.42TTL: 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 ConfigurationSingle IPv4 address configuration IPv4 Addresses 162.159.134.42TTL: 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. |
Info
No AAAA (IPv6) records found. While not required, IPv6 support is recommended for future-proofing your domain and improving accessibility for IPv6 users.
| Status | Test name | Information |
|---|---|---|
IPv6 Support | No AAAA (IPv6) records found. While not required, IPv6 support is recommended for future-proofing your domain and improving accessibility for IPv6 users. |
All nameservers are reporting the same mail server configuration. This consistency ensures reliable email delivery.
Mail Exchange Configuration
| Priority | Mail Server | Actions |
|---|---|---|
0 | sweetjames-com.mail.protection.outlook.com |
All mail server hostnames are properly formatted.
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.
Using managed mail services: Microsoft 365. PTR records are automatically managed by these providers.
| 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 | Mail Exchange Configuration
| |||||||
Mail Server Hostname Validation | All mail server hostnames are properly formatted. | |||||||
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 | Using managed mail services: Microsoft 365. PTR records are automatically managed by these providers. |
WWW record type: CNAME
www.
CNAME Record
sweetjames.com
Resolves To
IPv4 Resolution
162.159.134.42| Status | Test name | Information |
|---|---|---|
WWW Configuration | WWW record type: CNAME www. CNAME Record sweetjames.com Resolves To IPv4 Resolution 162.159.134.42 |
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 — none have external CNAME records. No subdomain takeover risk from dangling CNAMEs.
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 — none have external CNAME records. No subdomain takeover risk from dangling CNAMEs.
Learn more: https://dnschkr.com/blog/dns-attacks-guide#subdomain-takeover |
Info
Click any row to copy the raw value
v | spf1 mx include:_spf.salesforce.com include:spf.protection.outlook.com include:spf.US.exclaimer.net -all |
anthropic-domain-verification-dh89zm | aVt9t1h44Gi1I94VA4WSeIsYf |
google-site-verification | BtCOb6lDaJ7SXvXxcRjfUUCPKAVy3UZT0TKqaFhApBA |
Showing 3 of 3 records
Pass
Found SPF record: v=spf1 mx include:_spf.salesforce.com include:spf.protection.outlook.com include:spf.US.exclaimer.net -all
Pass
Found DMARC record: v=DMARC1; p=reject; rua=mailto:[email protected];
Click any row to copy the raw value
google-site-verification | BtCOb6lDaJ7SXvXxcRjfUUCPKAVy3UZT0TKqaFhApBA |
Showing 1 of 1 record
| Status | Test name | Information | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
TXT Records | Click any row to copy the raw value
Showing 3 of 3 records | |||||||||
SPF Record | Found SPF record: v=spf1 mx include:_spf.salesforce.com include:spf.protection.outlook.com include:spf.US.exclaimer.net -all | |||||||||
DMARC Record | Found DMARC record: v=DMARC1; p=reject; rua=mailto:[email protected]; | |||||||||
Domain Verification | Click any row to copy the raw value
Showing 1 of 1 record |