DNS Report for begmedia.com

• ns-1472.awsdns-56.org

  • IPv4: 205.251.197.192
  • IPv6: 2600:9000:5305:c000::1
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

• ns-1995.awsdns-57.co.uk

  • IPv4: 205.251.199.203
  • IPv6: 2600:9000:5307:cb00::1
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

• ns-93.awsdns-11.com

  • IPv4: 205.251.192.93
  • IPv6: 2600:9000:5300:5d00::1
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

• ns-983.awsdns-58.net

  • IPv4: 205.251.195.215
  • IPv6: 2600:9000:5303:d700::1
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

Nameserver Count - OK

• ns-1472.awsdns-56.org

  • Status: Responded
  • IP(s): 165.160.13.20
  • TTL: 300 seconds
  • Recursive Queries: Does not allow recursive queries
  • TCP Connectivity: TCP connection failed (Response code: REFUSED)

• ns-1995.awsdns-57.co.uk

  • Status: Responded
  • IP(s): 165.160.13.20
  • TTL: 300 seconds
  • Recursive Queries: Does not allow recursive queries
  • TCP Connectivity: TCP connection failed (Response code: REFUSED)

• ns-93.awsdns-11.com

  • Status: Responded
  • IP(s): 165.160.13.20
  • TTL: 300 seconds
  • Recursive Queries: Does not allow recursive queries
  • TCP Connectivity: TCP connection failed (Response code: REFUSED)

• ns-983.awsdns-58.net

  • Status: Responded
  • IP(s): 165.160.13.20
  • TTL: 300 seconds
  • Recursive Queries: Does not allow recursive queries
  • TCP Connectivity: TCP connection failed (Response code: REFUSED)

ns-1472.awsdns-56.org

• Serial: 1
• Refresh: 7200
• Retry: 900
• Expire: 1209600
• Minimum TTL: 86400

ns-1995.awsdns-57.co.uk

• Serial: 1
• Refresh: 7200
• Retry: 900
• Expire: 1209600
• Minimum TTL: 86400

ns-93.awsdns-11.com

• Serial: 1
• Refresh: 7200
• Retry: 900
• Expire: 1209600
• Minimum TTL: 86400

ns-983.awsdns-58.net

• Serial: 1
• Refresh: 7200
• Retry: 900
• Expire: 1209600
• Minimum TTL: 86400

Serial: 1 - OK

REFRESH: 7200 - OK

RETRY: 900 - OK

EXPIRE: 1209600 - OK

MINIMUM TTL: 86400 - Note: Outside recommended range (1-3 hours)

ns-1472.awsdns-56.org

• 0 begmedia-com.mail.protection.outlook.com ( 52.101.73.19 )
• 10 relay1.netnames.net ( 185.26.230.83 )
• 20 relay2.netnames.net ( 185.26.230.89 )

ns-1995.awsdns-57.co.uk

• 0 begmedia-com.mail.protection.outlook.com ( 52.101.68.27 )
• 10 relay1.netnames.net ( 185.26.230.83 )
• 20 relay2.netnames.net ( 185.26.230.89 )

ns-93.awsdns-11.com

• 0 begmedia-com.mail.protection.outlook.com ( 52.101.73.4 )
• 10 relay1.netnames.net ( 185.26.230.83 )
• 20 relay2.netnames.net ( 185.26.230.89 )

ns-983.awsdns-58.net

• 0 begmedia-com.mail.protection.outlook.com ( 52.101.73.26 )
• 10 relay1.netnames.net ( 185.26.230.83 )
• 20 relay2.netnames.net ( 185.26.230.89 )

MX Record Consistency - Warning: Inconsistencies found

MX Record Count - OK

• 4.73.101.52.in-addr.arpa -> mail-am0pr83cu00404.inbound.protection.outlook.com
• 19.73.101.52.in-addr.arpa -> mail-as8pr04cu00803.inbound.protection.outlook.com
• 26.73.101.52.in-addr.arpa -> mail-as9pr05cu01302.inbound.protection.outlook.com
• 83.230.26.185.in-addr.arpa -> relay1.netnames.net
• 89.230.26.185.in-addr.arpa -> relay2.netnames.net
• 27.68.101.52.in-addr.arpa -> mail-db7pr03cu00503.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 -all
• SPF Syntax: Passed
• Deprecated Elements: Passed
• IP Addresses:
• Includes: spf.protection.outlook.com
• DNS Lookups: 2
• Void Lookups: Passed
• Escaping Chars: Not Present
• All Mechanism: -all

• DKIM Records Found: No

Warnings:

• No DKIM records found for common selectors

• Record: None
• Syntax: Invalid
• Policy: None
• RUA (Aggregate Reports):

DMARC External Validation:

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

Errors:

• DMARC record does not exist