DNS Records for
dpictservices.pl
🐛 Hunting for rogue glue records.
DNS Records fordpictservices.pl
Domain DNS Health Score
88%
Total Tests
42
Passed
37
Critical Issues
1
Top Recommendations:
First-Visit DNS
~35ms
Excellent
Returning Visit
~0ms
Fully cached
CNAME Depth
None
Optimal
TTL Strategy
Balanced
TTL values are well-balanced across record types
DNS Provider
OVH
Avg NS Response
88ms
Normal
These nameservers are responsible for answering queries about your domain
2 Records
ns109.ovh.net
dns109.ovh.net
OVH
Your domain uses OVH's DNS infrastructure, providing reliable DNS hosting with their European-based network.
Source: This information was kindly provided by j-dns.pl 🙏🏼
Good. j-dns.pl 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 j-dns.pl
ns109.ovh.net
Nameserver
IPv4 Addresses:
5.135.67.9IPv6 Addresses:
2001:41d0:b00:fd00::2dns109.ovh.net
Nameserver
IPv4 Addresses:
5.196.41.217IPv6 Addresses:
2001:41d0:d01:300::2Note:
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 ns109.ovh.netdns109.ovh.netOVHYour domain uses OVH's DNS infrastructure, providing reliable DNS hosting with their European-based network. Source: This information was kindly provided by j-dns.pl 🙏🏼 | |
TLD Delegation Check | Good. j-dns.pl 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 j-dns.pl ns109.ovh.netNameserver IPv4 Addresses: 5.135.67.9IPv6 Addresses: 2001:41d0:b00:fd00::2dns109.ovh.netNameserver IPv4 Addresses: 5.196.41.217IPv6 Addresses: 2001:41d0:d01:300::2Note: 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. |
dns109.ovh.net
OVH
IPv4 Addresses
5.196.41.217
IPv6 Addresses
2001:41d0:d01:300::2
Authoritative
Non-Recursive
TCP
UDP
TTL: 86,400s (1 days)
ns109.ovh.net
OVH
IPv4 Addresses
5.135.67.9
IPv6 Addresses
2001:41d0:b00:fd00::2
Authoritative
Non-Recursive
TCP
UDP
TTL: 86,400s (1 days)
Good. No nameservers allow recursive queries.
The GLUE records from the parent zone match those from your nameservers. This is important for consistent DNS resolution.
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 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.
Good. Your nameservers are on different subnets, providing better redundancy as recommended by RFC2182 section 5.
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.
Good. All nameservers in your zone are properly registered at the parent. This ensures consistent DNS resolution for all users.
| Status | Test name | Information |
|---|---|---|
Nameserver Records from Zone | dns109.ovh.netOVH IPv4 Addresses 5.196.41.217 IPv6 Addresses 2001:41d0:d01:300::2 Authoritative Non-Recursive TCP UDP TTL: 86,400s (1 days) ns109.ovh.netOVH IPv4 Addresses 5.135.67.9 IPv6 Addresses 2001:41d0:b00:fd00::2 Authoritative Non-Recursive TCP UDP TTL: 86,400s (1 days) | |
Open Recursive Queries | Good. No nameservers allow recursive queries. | |
Glue Record Consistency | The GLUE records from the parent zone match those from your nameservers. This is important for consistent DNS resolution. | |
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 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 | Good. Your nameservers are on different subnets, providing better redundancy as recommended by RFC2182 section 5. | |
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 | Good. All nameservers in your zone are properly registered at the parent. This ensures consistent DNS resolution for all users. |
Info
Primary Nameserver
dns109.ovh.net
Hostmaster Email
tech.ovh.net
Serial Number
2075852222
Non-Standard (Unix Timestamp)
A unique version number that changes whenever the zone file is updated
Time Intervals
Refresh86400 seconds (1 days)
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)
Expire3600000 seconds (41 days)
How long secondary servers serve stale zone data (1w - 4w)
TTL60 seconds (1 minutes)
Default time-to-live for resource records (5m - 24h)
SOA Serial numbers per nameserver:
dns109.ovh.net: 2075852222
ns109.ovh.net: 2075852222
Good. All nameservers report the same SOA serial number.
Pass
OK. dns109.ovh.net is correctly listed as one of your nameservers.
Info
Your SOA serial number is: 2075852222.
Warning
Warning: SOA REFRESH interval is 86400 seconds (1440 minutes). This is above the recommended maximum of 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 3600000 seconds (41 days).
Warning: Common practice recommends a maximum of 28 days (2419200 seconds) to avoid stale data being served for too long.
Warning
Warning: SOA minimum TTL is 60 seconds (1 minutes). This is below the recommended minimum of 180 seconds as per RFC2308 section 4.
| Status | Test name | Information |
|---|---|---|
SOA record | Primary Nameserverdns109.ovh.net Hostmaster Emailtech.ovh.net Serial Number 2075852222 Non-Standard (Unix Timestamp) A unique version number that changes whenever the zone file is updated Time IntervalsRefresh86400 seconds (1 days) 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) Expire3600000 seconds (41 days) How long secondary servers serve stale zone data (1w - 4w) TTL60 seconds (1 minutes) Default time-to-live for resource records (5m - 24h) | |
SOA Serial Consistency | SOA Serial numbers per nameserver:
dns109.ovh.net: 2075852222
ns109.ovh.net: 2075852222
Good. All nameservers report the same SOA serial number. | |
SOA MNAME entry | OK. dns109.ovh.net is correctly listed as one of your nameservers. | |
SOA Serial | Your SOA serial number is: 2075852222. | |
SOA REFRESH | Warning: SOA REFRESH interval is 86400 seconds (1440 minutes). This is above the recommended maximum of 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 3600000 seconds (41 days).
Warning: Common practice recommends a maximum of 28 days (2419200 seconds) to avoid stale data being served for too long. | |
SOA MINIMUM TTL | Warning: SOA minimum TTL is 60 seconds (1 minutes). This is below the recommended minimum of 180 seconds as per RFC2308 section 4. |
IPv4 Configuration
Single IPv4 address configuration
IPv4 Addresses
45.82.123.122TTL: 3600s
Provides a good balance between propagation speed and DNS loadPass
TTL of 3600 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 45.82.123.122TTL: 3600s Provides a good balance between propagation speed and DNS load | |
A Record TTL | TTL of 3600 seconds provides a good balance between propagation speed and DNS load. |
IPv6 Configuration
Single IPv6 address configuration
IPv6 Addresses
2a0e:6a81:a:113::1TTL: 3600s
Provides a good balance between propagation speed and DNS load| Status | Test name | Information |
|---|---|---|
IPv6 Configuration | IPv6 ConfigurationSingle IPv6 address configuration IPv6 Addresses 2a0e:6a81:a:113::1TTL: 3600s 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.
Mail Exchange Configuration
| Priority | Mail Server | Actions |
|---|---|---|
10 | radon.dpictservices.pl | |
20 | helium.dpictservices.pl |
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 |
|---|---|
163.76.187.66.in-addr.arpa | radon.dpictservices.pl |
121.32.98.91.in-addr.arpa | helium.dpictservices.pl |
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 & AAAA
www.
A & AAAA Record
IPv4 Addresses
Matches Apex
45.82.123.122IPv6 Addresses
Matches Apex
2a0e:6a81:a:113::1| Status | Test name | Information |
|---|---|---|
WWW Configuration | WWW record type: A & AAAA www. A & AAAA Record IPv4 Addresses Matches Apex 45.82.123.122IPv6 Addresses Matches Apex 2a0e:6a81:a:113::1 |
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
Nameserver provider OVH is known to block zone transfers (AXFR). No test needed.
Learn more: https://dnschkr.com/blog/dns-attacks-guide#dns-zone-transfer-attack-axfr
Pass
Good. Tested notrealdnschkr.dpictservices.pl - No wildcard DNS records found, ensuring random subdomains won't resolve to an IP address.
Good. Tested notrealdnschkr.dpictservices.pl - Server returns NXDOMAIN for non-existent domains. While an SOA record is recommended, NXDOMAIN alone is a valid response.
Pass
Found CAA records:
└─ issuewild: sectigo.com
These records 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 | Nameserver provider OVH is known to block zone transfers (AXFR). No test needed.
Learn more: https://dnschkr.com/blog/dns-attacks-guide#dns-zone-transfer-attack-axfr | |
Wildcard DNS | Good. Tested notrealdnschkr.dpictservices.pl - No wildcard DNS records found, ensuring random subdomains won't resolve to an IP address. | |
NXDOMAIN Response | Good. Tested notrealdnschkr.dpictservices.pl - Server returns NXDOMAIN for non-existent domains. While an SOA record is recommended, NXDOMAIN alone is a valid response. | |
CAA Records | Found CAA records:
└─ issuewild: sectigo.com
These records 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 -all |
Showing 1 of 1 record
Pass
Found SPF record: v=spf1 mx -all
Pass
Found DMARC record: v=DMARC1;p=reject;pct=100;rua=mailto:[email protected];sp=reject;aspf=s;
| 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 -all | |||||
DMARC Record | Found DMARC record: v=DMARC1;p=reject;pct=100;rua=mailto:[email protected];sp=reject;aspf=s; |