my.com — DNS Report
C
70%
30
Pass
4
Warnings
1
Failures
5
Info
40
Total
Processed in 3s
● 📋 Domain Registration
PASS| Registrar | Moniker Online Services LLC |
| Registrar ID | 228 |
| Registry | Verisign |
| Registry ID | 2272009_DOMAIN_COM-VRSN |
| Created | Dec 16, 1994 |
| Updated | Nov 25, 2025 |
| Expires | Oct 19, 2028 (801 days left) |
| DNSSEC | ✗ Unsigned |
| Status | client transfer prohibited |
| RDAP Nameservers | ns1.my.com ns2.my.com |
● 🌐 DNS Records
PASSSOA Records (1)
| Name | Value | TTL |
|---|---|---|
| my.com | ns.my.com hostmaster.my.com 3576966047 60 900 604800 60 | 60 |
NS Records (2)
| Name | Value | TTL |
|---|---|---|
| my.com | ns1.my.com | 60 |
| my.com | ns2.my.com | 60 |
MX Records (1)
| Name | Value | TTL |
|---|---|---|
| my.com | mxs.mail.ru | 60 |
TXT Records (11)
| Name | Value | TTL |
|---|---|---|
| my.com | v=spf1 ip4:185.30.176.0/23 ip4:195.211.22.0/24 i nclude:mlrmr.com include:_spf.mail.ru ~all | 60 |
| my.com | google-site-verification=49GBAnIawfAdugGsrQ4O80tmX_WDr6POvb75XTsahtU | 60 |
| my.com | google-site-verification=IZvuBMGT2r5okkideNsuroLBIptNd-AXfxc4qJrgxVY | 60 |
| my.com | google-site-verification=lvfrpZMZ8GHXEonKdgdOubEmpzXITbhgKyWwbroEeTg | 60 |
| my.com | OSSRH-64681 | 60 |
| my.com | google-site-verification=gC5kIF9lVUqBAHfw6mbKRn8NQ6tMjnQ_6jfahupn_dM | 60 |
| my.com | 289134425-7447201 | 60 |
| my.com | HARICA-MeXPaeVdJMpYE8jE6ZC | 60 |
| my.com | HARICA-g2rjvR1NCSujbe802zP | 60 |
| my.com | _globalsign-domain-verification=82WMKkFVTO4ENPlHGfxhczQrjMqUuaMvoOPFgoSxZf | 60 |
| my.com | HARICA-B41kDE9z6AX6CFdRRlY | 60 |
CAA Records (7)
| Name | Value | TTL |
|---|---|---|
| my.com | 0 issue "letsencrypt.org" | 60 |
| my.com | 0 issue "harica.gr" | 60 |
| my.com | 0 issue "globalsign.com" | 60 |
| my.com | 0 issue "geotrust.com" | 60 |
| my.com | 0 issuewild "harica.gr" | 60 |
| my.com | 0 issue "pki.goog" | 60 |
| my.com | 0 issuewild "pki.goog" | 60 |
● 🔗 Parent Nameservers
PASS| Nameserver | IPv4 | IPv6 | Glue |
|---|---|---|---|
| ns1.my.com | 217.69.139.112 | - | Yes |
| ns2.my.com | 94.100.180.138 | - | Yes |
| ✓ | Nameservers Listed at Parent | The parent TLD nameserver has 2 nameserver(s) listed for my.com.ns1.my.com ns2.my.com |
| ✓ | Minimum Nameserver Count | 2 nameservers found. Good redundancy. |
| ✓ | Glue Record: ns1.my.com | Glue record found for ns1.my.com: 217.69.139.112 |
| ✓ | Public IP: ns1.my.com | Nameserver ns1.my.com has a public IP address. |
| ✓ | Glue Record: ns2.my.com | Glue record found for ns2.my.com: 94.100.180.138 |
| ✓ | Public IP: ns2.my.com | Nameserver ns2.my.com has a public IP address. |
| ✓ | Parent/Auth NS Consistency | The nameservers listed at the parent match those returned by the authoritative nameservers. |
● 🖥️ Authoritative Nameservers
INFO| Nameserver | UDP | TCP | Auth | Recursion | IPv6 | Latency |
|---|---|---|---|---|---|---|
| ns1.my.com | ✓ | ✓ | ✓ | Closed | - | 154ms |
| ns2.my.com | ✓ | ✓ | ✓ | Closed | - | 153ms |
| ✓ | Authoritative Nameservers Found | Found 2 authoritative nameserver(s): ns1.my.com, ns2.my.com |
| ✓ | All Nameservers Respond | All authoritative nameservers are responding to DNS queries. |
| ✓ | UDP DNS (Port 53) | At least one nameserver is responding to UDP DNS queries on port 53. |
| ✓ | TCP DNS (Port 53) | TCP DNS queries are supported. Required for large responses and DNSSEC. |
| ✓ | Authoritative Response | At least one nameserver returns an authoritative (AA) response for the zone. |
| ✓ | Open Recursion | Nameservers do not appear to answer recursive queries from outside. Good. |
| ✓ | Public IP Addresses | All nameservers have publicly routable IP addresses. |
| ℹ | IPv6 Support | No nameserver has an IPv6 (AAAA) address. IPv6 support is recommended. |
| ✓ | NS Record Consistency | All authoritative nameservers return identical NS records. |
| ✓ | Multiple Network Diversity | Nameservers appear to be on different subnets/networks. Good resilience. |
● 📄 SOA Record
WARNING| Primary NS (MNAME) | ns.my.com |
| Email (RNAME) | hostmaster.my.com |
| Serial | 3576966047 |
| Refresh | 60 (1 min) |
| Retry | 900 (15 min) |
| Expire | 604800 (7 days) |
| Minimum TTL | 60 (1 min) |
| ✓ | SOA Record Exists | SOA record found for my.com. |
| ⚠ | SOA MNAME | SOA MNAME (ns.my.com) is not in the NS records. This is normal for hidden primary configurations.NS records: ns1.my.com, ns2.my.com |
| ✓ | SOA RNAME | SOA contact email: hostmaster@my.com |
| ℹ | SOA Serial Format | SOA serial is 3576966047. The recommended format is YYYYMMDDNN (e.g., 2024010101). |
| ✓ | SOA Serial Consistency | All authoritative nameservers return the same SOA serial number. |
| ⚠ | SOA Refresh | SOA Refresh is 60 seconds. Values below 1200s are unusually low. |
| ⚠ | SOA Retry | SOA Retry (900s) is >= Refresh (60s). Retry should be less than Refresh. |
| ✓ | SOA Expire | SOA Expire is 604800 seconds (7 days). Reasonable value. |
| ✓ | SOA Minimum TTL | SOA Minimum TTL (negative caching) is 60 seconds. |
● 📧 Mail Servers (MX)
WARNING| Priority | Hostname | IPv4 | IPv6 | PTR |
|---|---|---|---|---|
| 10 | mxs.mail.ru | 217.69.139.150, 94.100.180.31 | - | mxs.mail.ru, mxs.mail.ru |
| ✓ | MX Records Exist | Found 1 MX record(s) for my.com. |
| ⚠ | MX Redundancy | Only one MX record found. A single mail server is a single point of failure. Consider adding a backup MX. |
| ✓ | MX Reverse DNS (PTR) | MX server(s) have PTR (reverse DNS) records. Many mail servers require rDNS for anti-spam. |
| ✓ | MX Consistency | All authoritative nameservers return consistent MX records. |
● 🌍 WWW / Web
FAIL| Target | Type | IPs |
|---|---|---|
| www.my.com | CNAME |
CNAME chain: www.my.com → my.com |
| ✗ | WWW CNAME Resolution | www.my.com is a CNAME to my.com, but the final target my.com has no A/AAAA records.CNAME chain: www.my.com → my.com |
● 🔒 DNSSEC
INFO| Enabled | No |
Chain of Trust
| Level | DS | DNSKEY | RRSIG | Status |
|---|---|---|---|---|
| . | — | ✓ | ✓ | PASS |
| com | ✓ | ✓ | ✓ | PASS |
| my.com | — | — | — | INFO |
| ℹ | DNSSEC Status | DNSSEC is not enabled for my.com. No DS or DNSKEY records found. |
● 🛡️ Email Security
INFOSPF (Sender Policy Framework)
| Record | v=spf1 ip4:185.30.176.0/23 ip4:195.211.22.0/24 include:mlrmr.com include:_spf.mail.ru ~all |
| All Mechanism | ~all |
| DNS Lookups | 2 / 10 max |
DMARC (Domain-based Message Authentication)
| Record | v=DMARC1;p=reject;rua=mailto:dmarc_rua@corp.mail.ru,mailto:rua@mlrmy.com; |
| Policy (p=) | reject |
| Aggregate Reports (rua) | mailto:dmarc_rua@corp.mail.ru,mailto:rua@mlrmy.com |
CAA (Certificate Authority Authorization)
| Flag | Tag | Value |
|---|---|---|
| 0 | issuewild | pki.goog |
| 0 | issue | pki.goog |
| 0 | issuewild | harica.gr |
| 0 | issue | geotrust.com |
| 0 | issue | globalsign.com |
| 0 | issue | harica.gr |
| 0 | issue | letsencrypt.org |
| ✓ | SPF Record | SPF record found.v=spf1 ip4:185.30.176.0/23 ip4:195.211.22.0/24 include:mlrmr.com include:_spf.mail.ru ~all |
| ℹ | SPF All Mechanism | SPF record uses '~all' (softfail). Non-listed senders will be marked but not rejected. Consider '-all' for strict enforcement. |
| ✓ | SPF DNS Lookup Count | SPF record uses approximately 2 DNS lookups (limit is 10). |
| ✓ | DMARC Record | DMARC record found.v=DMARC1;p=reject;rua=mailto:dmarc_rua@corp.mail.ru,mailto:rua@mlrmy.com; |
| ✓ | DMARC Policy | DMARC policy is 'reject'. Failing emails will be rejected. Maximum protection. |
| ✓ | DMARC Reporting (rua) | Aggregate reports (rua) will be sent to: mailto:dmarc_rua@corp.mail.ru,mailto:rua@mlrmy.com |
| ✓ | CAA Records | CAA records found (7). Certificate issuance is restricted. |
| ℹ | CAA iodef Tag | No 'iodef' CAA tag. Consider adding an iodef tag to receive reports of unauthorized certificate requests. |
● 📡 DNS Propagation
PASS| Status | Resolver | Location | Result | Latency |
|---|---|---|---|---|
| ℹ | Cloudflare (1.1.1.1) | US (Cloudflare) | No A records | 12ms |
| ℹ | Comodo Secure (8.26.56.26) | US (Comodo) | No A records | 203ms |
| ℹ | Google Public DNS 2 (8.8.4.4) | US (Google) | No A records | 204ms |
| ℹ | Quad9 (9.9.9.9) | US (Quad9) | No A records | 206ms |
| ℹ | Cloudflare 2 (1.0.0.1) | US (Cloudflare) | No A records | 249ms |
| ℹ | Yandex.DNS (77.88.8.8) | RU (Yandex) | No A records | 199ms |
| ℹ | Verisign (64.6.64.6) | US (Verisign) | No A records | 217ms |
| ℹ | OpenDNS (208.67.222.222) | US (OpenDNS) | No A records | 417ms |
| ℹ | Google Public DNS (8.8.8.8) | US (Google) | No A records | 203ms |
| ℹ | OpenDNS 2 (208.67.220.220) | US (OpenDNS) | No A records | 397ms |
● 🔄 Reverse DNS (PTR)
INFO| IP Address | PTR Record | Forward Match |
|---|---|---|
| 217.69.139.150 | mxs.mail.ru | ✓ Match |
| 94.100.180.31 | mxs.mail.ru | ✓ Match |