mohsinalam.com — DNS Report
B
84%
34
Pass
1
Warnings
0
Failures
5
Info
40
Total
Processed in 1s
● 📋 Domain Registration
PASS| Registrar | Spaceship, Inc. |
| Registrar ID | 3862 |
| Registry | Verisign |
| Registry ID | 1746399039_DOMAIN_COM-VRSN |
| Created | Sep 20, 2012 |
| Updated | Dec 08, 2023 |
| Expires | Sep 20, 2026 (41 days left) |
| DNSSEC | ✗ Unsigned |
| Status | client transfer prohibited |
| RDAP Nameservers | meg.ns.cloudflare.com moura.ns.cloudflare.com |
● 🌐 DNS Records
PASSSOA Records (1)
| Name | Value | TTL |
|---|---|---|
| mohsinalam.com | meg.ns.cloudflare.com dns.cloudflare.com 2409876940 10000 2400 604800 1800 | 1800 |
NS Records (2)
| Name | Value | TTL |
|---|---|---|
| mohsinalam.com | meg.ns.cloudflare.com | 86400 |
| mohsinalam.com | moura.ns.cloudflare.com | 86400 |
A Records (2)
| Name | Value | TTL |
|---|---|---|
| mohsinalam.com | 172.67.157.116 | 300 |
| mohsinalam.com | 104.21.73.37 | 300 |
AAAA Records (2)
| Name | Value | TTL |
|---|---|---|
| mohsinalam.com | 2606:4700:3035::6815:4925 | 300 |
| mohsinalam.com | 2606:4700:3036::ac43:9d74 | 300 |
MX Records (1)
| Name | Value | TTL |
|---|---|---|
| mohsinalam.com | mail.mohsinalam.com | 300 |
TXT Records (2)
| Name | Value | TTL |
|---|---|---|
| mohsinalam.com | brevo-code:1060d0c96c5848772a9c5d0226eb2bc8 | 300 |
| mohsinalam.com | v=spf1 include:spfdm-ap-southeast-1.aliyun.com ip4:117.55.230.206 include:spf.sg.aliyun.com ~all | 300 |
● 🔗 Parent Nameservers
PASS| Nameserver | IPv4 | IPv6 | Glue |
|---|---|---|---|
| moura.ns.cloudflare.com | 172.64.35.217, 162.159.44.217, 108.162.195.217 | 2606:4700:58::a29f:2cd9, 2a06:98c1:50::ac40:23d9, 2803:f800:50::6ca2:c3d9 | Yes |
| meg.ns.cloudflare.com | 173.245.58.196, 172.64.32.196, 108.162.192.196 | 2606:4700:50::adf5:3ac4, 2a06:98c1:50::ac40:20c4, 2803:f800:50::6ca2:c0c4 | Yes |
| ✓ | Nameservers Listed at Parent | The parent TLD nameserver has 2 nameserver(s) listed for mohsinalam.com.meg.ns.cloudflare.com moura.ns.cloudflare.com |
| ✓ | Minimum Nameserver Count | 2 nameservers found. Good redundancy. |
| ✓ | Glue Record: moura.ns.cloudflare.com | Glue record found for moura.ns.cloudflare.com: 108.162.195.217, 162.159.44.217, 172.64.35.217, 2606:4700:58::a29f:2cd9, 2803:f800:50::6ca2:c3d9, 2a06:98c1:50::ac40:23d9 |
| ✓ | Public IP: moura.ns.cloudflare.com | Nameserver moura.ns.cloudflare.com has a public IP address. |
| ✓ | Glue Record: meg.ns.cloudflare.com | Glue record found for meg.ns.cloudflare.com: 108.162.192.196, 172.64.32.196, 173.245.58.196, 2606:4700:50::adf5:3ac4, 2803:f800:50::6ca2:c0c4, 2a06:98c1:50::ac40:20c4 |
| ✓ | Public IP: meg.ns.cloudflare.com | Nameserver meg.ns.cloudflare.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
PASS| Nameserver | UDP | TCP | Auth | Recursion | IPv6 | Latency |
|---|---|---|---|---|---|---|
| meg.ns.cloudflare.com | ✓ | ✓ | ✓ | Closed | ✓ | 11ms |
| moura.ns.cloudflare.com | ✓ | ✓ | ✓ | Closed | ✓ | 12ms |
| ✓ | Authoritative Nameservers Found | Found 2 authoritative nameserver(s): moura.ns.cloudflare.com, meg.ns.cloudflare.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 | At least one nameserver has an IPv6 (AAAA) address. |
| ✓ | 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
INFO| Primary NS (MNAME) | meg.ns.cloudflare.com |
| Email (RNAME) | dns.cloudflare.com |
| Serial | 2409876940 |
| Refresh | 10000 (2h 46m) |
| Retry | 2400 (40 min) |
| Expire | 604800 (7 days) |
| Minimum TTL | 1800 (30 min) |
| ✓ | SOA Record Exists | SOA record found for mohsinalam.com. |
| ✓ | SOA MNAME | SOA MNAME (meg.ns.cloudflare.com) is listed as an authoritative nameserver. |
| ✓ | SOA RNAME | SOA contact email: dns@cloudflare.com |
| ℹ | SOA Serial Format | SOA serial is 2409876940. 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 10000 seconds (2h). Reasonable value. |
| ✓ | SOA Retry | SOA Retry is 2400 seconds. |
| ✓ | SOA Expire | SOA Expire is 604800 seconds (7 days). Reasonable value. |
| ✓ | SOA Minimum TTL | SOA Minimum TTL (negative caching) is 1800 seconds. |
● 📧 Mail Servers (MX)
WARNING| Priority | Hostname | IPv4 | IPv6 | PTR |
|---|---|---|---|---|
| 10 | mail.mohsinalam.com | 117.55.230.206 | - | host1.wpspike.com |
| ✓ | MX Records Exist | Found 1 MX record(s) for mohsinalam.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
INFO| Target | Type | IPs |
|---|---|---|
| www.mohsinalam.com | A | 172.67.157.116, 104.21.73.37, 2606:4700:3035::6815:4925, 2606:4700:3036::ac43:9d74 |
| ✓ | WWW Record | www.mohsinalam.com resolves to: 172.67.157.116, 104.21.73.37, 2606:4700:3035::6815:4925, 2606:4700:3036::ac43:9d74 |
| ℹ | WWW vs Apex IP | www.mohsinalam.com and mohsinalam.com resolve to different IP addresses. This is normal if they are intentionally served differently. |
● 🔒 DNSSEC
INFO| Enabled | No |
Chain of Trust
| Level | DS | DNSKEY | RRSIG | Status |
|---|---|---|---|---|
| . | — | ✓ | ✓ | PASS |
| com | ✓ | ✓ | ✓ | PASS |
| mohsinalam.com | — | — | — | INFO |
| ℹ | DNSSEC Status | DNSSEC is not enabled for mohsinalam.com. No DS or DNSKEY records found. |
● 🛡️ Email Security
INFOSPF (Sender Policy Framework)
| Record | v=spf1 include:spfdm-ap-southeast-1.aliyun.com ip4:117.55.230.206 include:spf.sg.aliyun.com ~all |
| All Mechanism | ~all |
| DNS Lookups | 2 / 10 max |
DMARC (Domain-based Message Authentication)
| Record | v=DMARC1; p=reject; rua=mailto:dmarc_report@service.aliyun.com,mailto:rua@dmarc.brevo.com; |
| Policy (p=) | reject |
| Aggregate Reports (rua) | mailto:dmarc_report@service.aliyun.com,mailto:rua@dmarc.brevo.com |
CAA (Certificate Authority Authorization)
No CAA records found. Any certificate authority can issue SSL certificates for this domain.
| ✓ | SPF Record | SPF record found.v=spf1 include:spfdm-ap-southeast-1.aliyun.com ip4:117.55.230.206 include:spf.sg.aliyun.com ~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_report@service.aliyun.com,mailto:rua@dmarc.brevo.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_report@service.aliyun.com,mailto:rua@dmarc.brevo.com |
| ℹ | CAA Records | No CAA records found for mohsinalam.com. CAA records specify which certificate authorities may issue SSL/TLS certificates for this domain. |
● 📡 DNS Propagation
PASS| Status | Resolver | Location | Result | Latency |
|---|---|---|---|---|
| ✓ | Comodo Secure (8.26.56.26) | US (Comodo) | 172.67.157.116, 104.21.73.37 | 27ms |
| ✓ | Cloudflare (1.1.1.1) | US (Cloudflare) | 104.21.73.37, 172.67.157.116 | 31ms |
| ✓ | Google Public DNS (8.8.8.8) | US (Google) | 104.21.73.37, 172.67.157.116 | 33ms |
| ✓ | Google Public DNS 2 (8.8.4.4) | US (Google) | 172.67.157.116, 104.21.73.37 | 35ms |
| ✓ | Quad9 (9.9.9.9) | US (Quad9) | 104.21.73.37, 172.67.157.116 | 31ms |
| ✓ | OpenDNS 2 (208.67.220.220) | US (OpenDNS) | 104.21.73.37, 172.67.157.116 | 29ms |
| ✓ | OpenDNS (208.67.222.222) | US (OpenDNS) | 172.67.157.116, 104.21.73.37 | 43ms |
| ✓ | Verisign (64.6.64.6) | US (Verisign) | 104.21.73.37, 172.67.157.116 | 44ms |
| ✓ | Cloudflare 2 (1.0.0.1) | US (Cloudflare) | 104.21.73.37, 172.67.157.116 | 152ms |
| ✓ | Yandex.DNS (77.88.8.8) | RU (Yandex) | 104.21.73.37, 172.67.157.116 | 306ms |
● 🔄 Reverse DNS (PTR)
INFO| IP Address | PTR Record | Forward Match |
|---|---|---|
| 117.55.230.206 | host1.wpspike.com | ✗ No match |