DNS Report for smg.com

• ns1-01.azure-dns.com

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

• ns2-01.azure-dns.net

  • IPv4: 150.171.21.1
  • IPv6: 2620:1ec:8ec:700::1
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

• ns3-01.azure-dns.org

  • IPv4: 204.14.183.1
  • IPv6: 2a01:111:4000:700::1
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

• ns4-01.azure-dns.info

  • IPv4: 208.84.5.1
  • IPv6: 2620:1ec:bda:700::1
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

Nameserver Count - OK

• ns1-01.azure-dns.com

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

• ns2-01.azure-dns.net

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

• ns3-01.azure-dns.org

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

• ns4-01.azure-dns.info

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

ns1-01.azure-dns.com

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

ns2-01.azure-dns.net

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

ns3-01.azure-dns.org

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

ns4-01.azure-dns.info

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

Serial: 1 - OK

REFRESH: 3600 - OK

RETRY: 300 - OK

EXPIRE: 2419200 - OK

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

ns1-01.azure-dns.com

• 10 mail.servicemanagement.com ( 144.86.188.50 )
• 15 mail4.servicemanagement.com ( 68.177.189.150 )
• 20 mail2.servicemanagement.com ( 144.86.188.55 )
• 30 mail3.servicemanagement.com ( 68.177.188.9 )

ns2-01.azure-dns.net

• 10 mail.servicemanagement.com ( 144.86.188.50 )
• 15 mail4.servicemanagement.com ( 68.177.189.150 )
• 20 mail2.servicemanagement.com ( 144.86.188.55 )
• 30 mail3.servicemanagement.com ( 68.177.188.9 )

ns3-01.azure-dns.org

• 10 mail.servicemanagement.com ( 144.86.188.50 )
• 15 mail4.servicemanagement.com ( 68.177.189.150 )
• 20 mail2.servicemanagement.com ( 144.86.188.55 )
• 30 mail3.servicemanagement.com ( 68.177.188.9 )

ns4-01.azure-dns.info

• 10 mail.servicemanagement.com ( 144.86.188.50 )
• 15 mail4.servicemanagement.com ( 68.177.189.150 )
• 20 mail2.servicemanagement.com ( 144.86.188.55 )
• 30 mail3.servicemanagement.com ( 68.177.188.9 )

MX Record Consistency - OK

MX Record Count - OK

• 50.188.86.144.in-addr.arpa -> mail.servicemanagement.com
• 55.188.86.144.in-addr.arpa -> webmail.servicemanagement.com
• 9.188.177.68.in-addr.arpa -> No PTR record found: The DNS query name does not exist: 9.188.177.68.in-addr.arpa.
• 150.189.177.68.in-addr.arpa -> mail4.servicemanagement.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 mx ip4:144.86.188.0/24 ip4:66.22.187.0/22 ip4:68.177.188.0/22 mx:cxbuyerinsights.com include:_spf.salesforce.com include:23425093.spf04.hubspotemail.net include:mail.zendesk.com ?all
• SPF Syntax: Failed
• Deprecated Elements: Passed
• IP Addresses: 144.86.188.0/24, 66.22.187.0/22, 68.177.188.0/22
• Includes: _spf.salesforce.com, 23425093.spf04.hubspotemail.net, mail.zendesk.com
• DNS Lookups: 9
• Void Lookups: Passed
• Escaping Chars: Not Present
• All Mechanism: ?all

Errors:

• SPF record syntax is invalid

• DKIM Records Found: Yes
• Selectors Found: selector2
• Selector 'selector2':
  Record: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC1Ch5s7Z1TL1l7EYgCShpDGJc8Zbj4fFO89tqw+WLqgo6wbF/igUQQk+xVglj6qZWwOPoKmkvqCq6m1jkOlK89fomhQspdvc5cDqOzAFNoUj4+OnhMti30S1adhdxrrQqJpMlNwhN1DJST2xJKJnutFs4zAHp+i8HMsmTQiJ7FjQIDAQAB;
• Valid Syntax: Yes

• Record: v=DMARC1; p=none; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected]
• Syntax: Valid
• Policy: none
• RUA (Aggregate Reports): mailto:[email protected], mailto:[email protected]
• RUF (Forensic Reports): mailto:[email protected]

DMARC External Validation:

• Valid external domains: mxtoolbox.dmarc-report.com, vali.email, forensics.dmarc-report.com
• All external domains in your DMARC record are giving permission to send them DMARC reports.