DNS Report for cyberpower.com

• ns2.cyberpower.com

  • IPv4: 61.218.20.141
  • IPv6: No IPv6 found
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): N/A seconds
  • Recursive: N/A

• ns3.cyberpower.com

  • IPv4: 52.162.160.52
  • IPv6: No IPv6 found
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): N/A seconds
  • Recursive: N/A

• ns1.cyberpower.com

  • IPv4: 211.21.12.128
  • IPv6: No IPv6 found
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): N/A seconds
  • Recursive: N/A

• ns1-04.azure-dns.com

  • IPv4: 13.107.236.4
  • IPv6: 2603:1061:0:700::4
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

Nameserver Count - OK

• ns2.cyberpower.com

  • Status: Responded
  • IP(s): 138.91.43.198
  • TTL: 3600 seconds
  • Recursive Queries: Unclear (Response code: NOERROR)
  • TCP Connectivity: Allows TCP connections

• ns3.cyberpower.com

  • Status: Responded
  • IP(s): 138.91.43.198
  • TTL: 3600 seconds
  • Recursive Queries: Unclear (Response code: NOERROR)
  • TCP Connectivity: Allows TCP connections

• ns1.cyberpower.com

  • Status: Responded
  • IP(s): 138.91.43.198
  • TTL: 3600 seconds
  • Recursive Queries: Unclear (Response code: NOERROR)
  • TCP Connectivity: Allows TCP connections

• ns1-04.azure-dns.com

  • Status: Responded
  • IP(s): 138.91.43.198
  • TTL: 3600 seconds
  • Recursive Queries: Unclear (Response code: NOERROR)
  • TCP Connectivity: Allows TCP connections

ns2.cyberpower.com

• Serial: 1424137817
• Refresh: 7200
• Retry: 900
• Expire: 2419200
• Minimum TTL: 3600

ns3.cyberpower.com

• Serial: 1424137817
• Refresh: 7200
• Retry: 900
• Expire: 2419200
• Minimum TTL: 3600

ns1.cyberpower.com

• Serial: 1424137817
• Refresh: 7200
• Retry: 900
• Expire: 2419200
• Minimum TTL: 3600

ns1-04.azure-dns.com

• Serial: 1
• Refresh: 3600
• Retry: 300
• Expire: 2419200
• Minimum TTL: 300

Serial - Warning: Inconsistent across nameservers

REFRESH - Warning: Inconsistent across nameservers

RETRY - Warning: Inconsistent across nameservers

EXPIRE: 2419200 - OK

MINIMUM TTL - Warning: Inconsistent across nameservers

ns2.cyberpower.com

• 10 cyberpower-com.mail.protection.outlook.com ( 52.101.132.30 )

ns3.cyberpower.com

• 10 cyberpower-com.mail.protection.outlook.com ( 52.101.132.28 )

ns1.cyberpower.com

• 10 cyberpower-com.mail.protection.outlook.com ( 52.101.137.2 )

ns1-04.azure-dns.com

• 10 cyberpower-com.mail.protection.outlook.com ( 52.101.132.28 )

MX Record Consistency - Warning: Inconsistencies found

MX Record Count - Warning: Only one MX record

• 2.137.101.52.in-addr.arpa -> No PTR record found: The DNS query name does not exist: 2.137.101.52.in-addr.arpa.
• 30.132.101.52.in-addr.arpa -> mail-hk3pr03cu00106.inbound.protection.outlook.com
• 28.132.101.52.in-addr.arpa -> mail-hk2pr02cu00104.inbound.protection.outlook.com

PTR Records - OK

• Signed: No
• Validation: Failed
• DNSKEY Records: None
• DS Records in parent zone: None
• DS at Parent: None

DNSSEC - Note: Domain is not signed with DNSSEC

Error: No DNSSEC records found

SPF Record Published: Passed

Multiple SPF Records: Passed

SPF Record 1:

• Record: v=spf1 include:spf.protection.outlook.com include:_spf.salesforce.com include:icpbounce.com include:bmsend.com include:customers.clickdimensions.com include:_spf.messagegears.net a:mail.cyberpower.com include:mailgun.org include:_spf-amer.onbmc.com
• SPF Syntax: Passed
• Deprecated Elements: Passed
• IP Addresses:
• Includes: spf.protection.outlook.com, _spf.salesforce.com, icpbounce.com, bmsend.com, customers.clickdimensions.com, _spf.messagegears.net, mailgun.org, _spf-amer.onbmc.com
• DNS Lookups: 15 (Warning: Exceeds limit)
• Void Lookups: Passed
• Escaping Chars: Not Present
• All Mechanism: Not Present

Warnings:

• SPF record doesn't contain an 'all' mechanism
• SPF record has more than 10 DNS lookups, which may cause lookup limits

• DKIM Records Found: No

Warnings:

• No DKIM records found for common selectors

• Record: v=DMARC1;p=none;pct=100
• Syntax: Valid
• Policy: none
• Percent: 100%
• RUA (Aggregate Reports):

DMARC External Validation:

• All external domains in your DMARC record are giving permission to send them DMARC reports.