DNS Records for
anrf.gov.ma
🐛 Hunting for rogue glue records.
DNS Records foranrf.gov.ma
Domain DNS Health Score
83%
Total Tests
41
Passed
34
Critical Issues
2
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
DNS Provider
Avg NS Response
100ms
Slow
Insights
A1
AAAA0
NS3
MX2
TXT1
SPFok
DMARCok
DNSSECfail
CAAinfo
86%
43/50 tests
TTL cache lifetime
1m
5m
30m
1h
4h
1d
2d
7d
A
High TTL (2h). Great for stable IPs, but changes take longer to propagate.2 hr
NS
2h — appropriate for nameserver records.2 hr
MX
2h — appropriate for mail server records.2 hr
SOA
2 hr
TXT
2h — appropriate for TXT records.2 hr
Resolution waterfall
First visit ~35msReturning ~0ms
Root → TLD nameserver
5ms
TLD → Authoritative NS
20ms
NS → A record (apex)
15ms
Benchmark: excellent
Per-nameserver response time
avg 100msspread 12ms
ns3.wanamaroc.com
96ms
loukos2.wanacorp.com
96ms
ns2.wanamaroc.com
108ms
Provider DNS Provider
www resolution
www.anrf.gov.maDirect A record — no CNAME chain
41.137.128.41SOA timing
Serial
2021062523Refresh
2 hr
How often secondaries re-check
Retry
1 hr
Wait after a failed refresh
Expire
7 days
Secondaries stop serving after
Min TTL
2 hr
Negative cache duration
Zone last updated
~1755 days ago
Negative cache
NXDOMAIN responses are cached for 2 hr. Typos against this zone stick around that long.
Glue records at parent
via a.tld.ma
| Nameserver | IPv4 | IPv6 | Zone match |
|---|---|---|---|
| ns2.wanamaroc.com | 105.73.3.67 | — | match |
| ns3.wanamaroc.com | 105.73.3.68 | — | match |
Mail exchange priority
2 MX records
pref 10
smtp01.anrf.gov.ma
PrimaryTied priority
pref 10
smtp2.anrf.gov.ma
PrimaryTied priority
SPF mechanism chain
v=spf1
mxSenders matching domain's MX
aSenders matching domain's A
a:smtp1.anrf.gov.maSenders matching domain's A
a:smtp2.anrf.gov.maSenders matching domain's A
ip4:41.137.128.44/32IPv4 range allowed
ip4:41.137.128.46/32IPv4 range allowed
-allhardfail
DMARC policy
Policy (p=)
quarantine
Fraudulent mail routed to spam
Subdomains (sp=)
quarantine
Inherits from p=
Coverage (pct=)
100%
Applied to all mail
SPF alignment
strict
DKIM alignment
strict
Aggregate reports → rua
mailto:[email protected]
These nameservers are responsible for answering queries about your domain
2 Records
ns2.wanamaroc.com
ns3.wanamaroc.com
Source: This information was kindly provided by a.tld.ma 🙏🏼
Good. a.tld.ma has information for your TLD. This confirms your domain is properly delegated.
Warning
Warning: Mismatch between parent nameservers and actual NS records.
NS-only nameservers (in NS records but not listed at parent):
• loukos2.wanacorp.com
This inconsistency can cause DNS resolution issues and should be resolved by updating either the parent nameservers or the NS records.
Glue Records from Parent Server
Information provided by a.tld.ma
ns2.wanamaroc.com
Nameserver
IPv4 Addresses:
105.73.3.67ns3.wanamaroc.com
Nameserver
IPv4 Addresses:
105.73.3.68Note:
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 ns2.wanamaroc.comns3.wanamaroc.comSource: This information was kindly provided by a.tld.ma 🙏🏼 | |
TLD Delegation Check | Good. a.tld.ma has information for your TLD. This confirms your domain is properly delegated. | |
Nameservers Listed at Parent | Warning: Mismatch between parent nameservers and actual NS records.
NS-only nameservers (in NS records but not listed at parent):
• loukos2.wanacorp.com
This inconsistency can cause DNS resolution issues and should be resolved by updating either the parent nameservers or the NS records. | |
Glue Records from Parent | Glue Records from Parent ServerInformation provided by a.tld.ma ns2.wanamaroc.comNameserver IPv4 Addresses: 105.73.3.67ns3.wanamaroc.comNameserver IPv4 Addresses: 105.73.3.68Note: 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. |
ns3.wanamaroc.com
IPv4 Addresses
105.73.3.68
Authoritative
Non-Recursive
TCP
UDP
TTL: 28,800s (0.3 days)
loukos2.wanacorp.com
IPv4 Addresses
105.73.34.29
Authoritative
Non-Recursive
TCP
UDP
TTL: 28,800s (0.3 days)
ns2.wanamaroc.com
IPv4 Addresses
105.73.3.67
Authoritative
Non-Recursive
TCP
UDP
TTL: 28,800s (0.3 days)
Good. No nameservers allow recursive queries.
Warning
Warning: Mismatched IPv4 records between parent and nameserver responses. This can cause inconsistent DNS resolution.
Mismatches found:
• loukos2.wanacorp.com:
IPv4: Parent has [], Nameserver has [105.73.34.29]
Note: Your nameservers are not under your domain, so additional glue records are not required.
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 3 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.
Error: The following nameservers are missing from parent zone:
loukos2.wanacorp.com
This inconsistency can cause DNS resolution problems. See RFC1034 section 3.6 for proper delegation requirements.
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.
Warning
Found 3 pair(s) of nameserver IPs in the same /16 subnet. For better redundancy, consider using nameservers on different subnets as recommended by RFC2182 section 5. Affected pairs: 105.73.3.68 and 105.73.34.29, 105.73.3.68 and 105.73.3.67, 105.73.34.29 and 105.73.3.67. Note: providers using anycast may have geographic redundancy despite shared subnets.
Good. All nameserver IPs (both IPv4 and IPv6) are public, ensuring global accessibility as required by RFC1035.
Good. All DNS servers allow TCP connections, which is required for larger DNS responses as per RFC1035.
Good. All DNS servers allow UDP connections, which is required for standard DNS queries.
Good. Your nameservers appear to be on different networks, providing better redundancy.
Warning
Warning: Found stealth nameservers:
Nameservers in zone but missing from parent:
• loukos2.wanacorp.com
Stealth nameservers can cause inconsistent DNS resolution and should be either properly registered at both parent and zone, or removed.
| Status | Test name | Information |
|---|---|---|
Nameserver Records from Zone | ns3.wanamaroc.comIPv4 Addresses 105.73.3.68 Authoritative Non-Recursive TCP UDP TTL: 28,800s (0.3 days) loukos2.wanacorp.comIPv4 Addresses 105.73.34.29 Authoritative Non-Recursive TCP UDP TTL: 28,800s (0.3 days) ns2.wanamaroc.comIPv4 Addresses 105.73.3.67 Authoritative Non-Recursive TCP UDP TTL: 28,800s (0.3 days) | |
Open Recursive Queries | Good. No nameservers allow recursive queries. | |
Glue Record Consistency | Warning: Mismatched IPv4 records between parent and nameserver responses. This can cause inconsistent DNS resolution.
Mismatches found:
• loukos2.wanacorp.com:
IPv4: Parent has [], Nameserver has [105.73.34.29] | |
Missing Glue for NS Records | Note: Your nameservers are not under your domain, so additional glue records are not required. | |
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 3 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 | Error: The following nameservers are missing from parent zone:
loukos2.wanacorp.com
This inconsistency can cause DNS resolution problems. See RFC1034 section 3.6 for proper delegation requirements. | |
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 | Found 3 pair(s) of nameserver IPs in the same /16 subnet. For better redundancy, consider using nameservers on different subnets as recommended by RFC2182 section 5. Affected pairs: 105.73.3.68 and 105.73.34.29, 105.73.3.68 and 105.73.3.67, 105.73.34.29 and 105.73.3.67. Note: providers using anycast may have geographic redundancy despite shared subnets. | |
NS IP Public Accessibility | Good. All nameserver IPs (both IPv4 and IPv6) are public, ensuring global accessibility as required by RFC1035. | |
DNS servers allow TCP connection | Good. All DNS servers allow TCP connections, which is required for larger DNS responses as per RFC1035. | |
DNS servers allow UDP connection | Good. All DNS servers allow UDP connections, which is required for standard DNS queries. | |
NS AS Diversity Check | Good. Your nameservers appear to be on different networks, providing better redundancy. | |
Stealth Nameserver Check | Warning: Found stealth nameservers:
Nameservers in zone but missing from parent:
• loukos2.wanacorp.com
Stealth nameservers can cause inconsistent DNS resolution and should be either properly registered at both parent and zone, or removed. |
Info
Primary Nameserver
ns2.wanamaroc.com
Hostmaster Email
hostmaster.wanamaroc.com
Serial Number
2021062523
Standard Format (YYYYMMDDnn)
A unique version number that changes whenever the zone file is updated
Time Intervals
Refresh7200 seconds (2 hours)
How often secondary nameservers check for updates (20m - 24h)
Retry3600 seconds (1 hours)
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)
TTL7200 seconds (2 hours)
Default time-to-live for resource records (5m - 24h)
SOA Serial numbers per nameserver:
ns3.wanamaroc.com: 2021062523
loukos2.wanacorp.com: 2021062523
ns2.wanamaroc.com: 2021062523
Good. All nameservers report the same SOA serial number.
Pass
OK. ns2.wanamaroc.com is correctly listed as one of your nameservers.
Info
Your SOA serial number is: 2021062523.
Pass
OK. Your SOA REFRESH interval is: 7200 seconds (120 minutes). This is within the recommended range of 1200-43200 seconds as per RFC1912 section 2.2.
Pass
OK. Your SOA RETRY value is: 3600 seconds (60 minutes). This is within the recommended range of 120-7200 seconds as per RFC1912 section 2.2.
Warning
Current expire time is 604800 seconds (7 days).
Warning: Common practice recommends a minimum of 14 days (1209600 seconds) to ensure secondary servers can continue serving during extended outages.
Pass
OK. Your SOA MINIMUM TTL is: 7200 seconds (120 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 Nameserverns2.wanamaroc.com Hostmaster Emailhostmaster.wanamaroc.com Serial Number 2021062523 Standard Format (YYYYMMDDnn) A unique version number that changes whenever the zone file is updated Time IntervalsRefresh7200 seconds (2 hours) How often secondary nameservers check for updates (20m - 24h) Retry3600 seconds (1 hours) 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) TTL7200 seconds (2 hours) Default time-to-live for resource records (5m - 24h) | |
SOA Serial Consistency | SOA Serial numbers per nameserver:
ns3.wanamaroc.com: 2021062523
loukos2.wanacorp.com: 2021062523
ns2.wanamaroc.com: 2021062523
Good. All nameservers report the same SOA serial number. | |
SOA MNAME entry | OK. ns2.wanamaroc.com is correctly listed as one of your nameservers. | |
SOA Serial | Your SOA serial number is: 2021062523. | |
SOA REFRESH | OK. Your SOA REFRESH interval is: 7200 seconds (120 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: 3600 seconds (60 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).
Warning: Common practice recommends a minimum of 14 days (1209600 seconds) to ensure secondary servers can continue serving during extended outages. | |
SOA MINIMUM TTL | OK. Your SOA MINIMUM TTL is: 7200 seconds (120 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
41.137.128.41TTL: 7200s
Provides a good balance between propagation speed and DNS loadPass
TTL of 7200 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 41.137.128.41TTL: 7200s Provides a good balance between propagation speed and DNS load | |
A Record TTL | TTL of 7200 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 |
|---|---|---|
10 | smtp01.anrf.gov.ma | |
10 | smtp2.anrf.gov.ma |
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.
Reverse DNS Records
All Valid
| PTR Query | Hostname |
|---|---|
44.128.137.41.in-addr.arpa | smtp1.utrf.gov.ma |
46.128.137.41.in-addr.arpa | smtp2.utrf.gov.ma |
Proper reverse DNS records are essential for email deliverability. Mail servers often check if sending IPs have matching PTR records.
| 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 | Reverse DNS RecordsAll Valid
Proper reverse DNS records are essential for email deliverability. Mail servers often check if sending IPs have matching PTR records. |
WWW record type: A
www.
A Record
IPv4 Addresses
Matches Apex
41.137.128.41| Status | Test name | Information |
|---|---|---|
WWW Configuration | WWW record type: A www. A Record IPv4 Addresses Matches Apex 41.137.128.41 |
Error
DNSSEC validation failed. This indicates a problem with your DNSSEC configuration:
• DNSKEY query failed with SERVFAIL
• DS query failed with SERVFAIL
Please check your DNSSEC configuration with your DNS provider.
Pass
Zone transfer (AXFR) is properly restricted. Tested 3 nameservers — all refused the transfer request.
Learn more: https://dnschkr.com/blog/dns-attacks-guide#dns-zone-transfer-attack-axfr
Pass
Good. Tested notrealdnschkr.anrf.gov.ma - No wildcard DNS records found, ensuring random subdomains won't resolve to an IP address.
Good. Tested notrealdnschkr.anrf.gov.ma - Server returns NXDOMAIN for non-existent domains. While an SOA record is recommended, NXDOMAIN alone is a valid response.
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 | DNSSEC validation failed. This indicates a problem with your DNSSEC configuration:
• DNSKEY query failed with SERVFAIL
• DS query failed with SERVFAIL
Please check your DNSSEC configuration with your DNS provider. | |
Zone Transfer | Zone transfer (AXFR) is properly restricted. Tested 3 nameservers — all refused the transfer request.
Learn more: https://dnschkr.com/blog/dns-attacks-guide#dns-zone-transfer-attack-axfr | |
Wildcard DNS | Good. Tested notrealdnschkr.anrf.gov.ma - No wildcard DNS records found, ensuring random subdomains won't resolve to an IP address. | |
NXDOMAIN Response | Good. Tested notrealdnschkr.anrf.gov.ma - Server returns NXDOMAIN for non-existent domains. While an SOA record is recommended, NXDOMAIN alone is a valid response. | |
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 a a:smtp1.anrf.gov.ma a:smtp2.anrf.gov.ma ip4:41.137.128.44/32 ip4:41.137.128.46/32 -all |
Showing 1 of 1 record
Pass
Found SPF record: v=spf1 mx a a:smtp1.anrf.gov.ma a:smtp2.anrf.gov.ma ip4:41.137.128.44/32 ip4:41.137.128.46/32 -all
Pass
Found DMARC record: v=DMARC1; p=quarantine; aspf=s; adkim=s; pct=100; rua=mailto:[email protected]; fo=0; ri=604800
| 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 mx a a:smtp1.anrf.gov.ma a:smtp2.anrf.gov.ma ip4:41.137.128.44/32 ip4:41.137.128.46/32 -all | |||||
DMARC Record | Found DMARC record: v=DMARC1; p=quarantine; aspf=s; adkim=s; pct=100; rua=mailto:[email protected]; fo=0; ri=604800 |