DNS Report for bankmandiri.co.id

• ns01.bankmandiri.co.id

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

• ns02.bankmandiri.co.id

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

• ns1.bankmandiri.co.id

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

Nameserver Count - OK

• ns01.bankmandiri.co.id

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

• ns02.bankmandiri.co.id

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

• ns1.bankmandiri.co.id

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

ns01.bankmandiri.co.id

• Serial: 2018122777
• Refresh: 10800
• Retry: 3600
• Expire: 2419200
• Minimum TTL: 900

ns02.bankmandiri.co.id

• Serial: 2018122777
• Refresh: 10800
• Retry: 3600
• Expire: 2419200
• Minimum TTL: 900

ns1.bankmandiri.co.id

• Serial: 2018122777
• Refresh: 10800
• Retry: 3600
• Expire: 2419200
• Minimum TTL: 900

Serial: 2018122777 - OK

REFRESH: 10800 - OK

RETRY: 3600 - OK

EXPIRE: 2419200 - OK

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

ns01.bankmandiri.co.id

• 0 mg1p.mail.bankmandiri.co.id ( 103.139.82.166 )
• 0 mg1r.mail.bankmandiri.co.id ( 103.139.83.166 )
• 100 mx1.hc630-57.ap.iphmx.com ( 139.138.29.219 )
• 100 mx2.hc630-57.ap.iphmx.com ( 139.138.29.219 )

ns02.bankmandiri.co.id

• 0 mg1p.mail.bankmandiri.co.id ( 103.139.82.166 )
• 0 mg1r.mail.bankmandiri.co.id ( 103.139.83.166 )
• 100 mx1.hc630-57.ap.iphmx.com ( 139.138.29.219 )
• 100 mx2.hc630-57.ap.iphmx.com ( 139.138.29.219 )

ns1.bankmandiri.co.id

• 0 mg1p.mail.bankmandiri.co.id ( 103.139.82.166 )
• 0 mg1r.mail.bankmandiri.co.id ( 103.139.83.166 )
• 100 mx1.hc630-57.ap.iphmx.com ( 139.138.29.219 )
• 100 mx2.hc630-57.ap.iphmx.com ( 139.138.29.219 )

MX Record Consistency - OK

MX Record Count - OK

• 219.29.138.139.in-addr.arpa -> esa.hc630-57.ap.iphmx.com
• 166.83.139.103.in-addr.arpa -> mg1r.mail.bankmandiri.co.id
• 219.29.138.139.in-addr.arpa -> esa.hc630-57.ap.iphmx.com
• 166.82.139.103.in-addr.arpa -> mg1p.mail.bankmandiri.co.id

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:bankmandiri.co.id include:_spf.bankmandiri.co.id -all
• SPF Syntax: Passed
• Deprecated Elements: Passed
• IP Addresses:
• Includes: _spf.bankmandiri.co.id
• DNS Lookups: 7
• Void Lookups: Passed
• Escaping Chars: Not Present
• All Mechanism: -all

• DKIM Records Found: Yes
• Selectors Found: selector2
• Selector 'selector2':
  Record: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDgwk3Zi1aMIkl7gRvXDCDVL9v5tQZ0hAZUriqTeeLEFbEGaTOBenaP0ZUFbvsn8WkqgS+lDPxPiLT002+SP04oCS7+hp8q2RULTY44lWnnjIGzqHUY90VgAYLX2SVF/zcNhDREBPZo9/sU78UW2ecwFtZblitfggt7vOKriesfLQIDAQAB;
• Valid Syntax: Yes

• Record: v=DMARC1; p=quarantine; sp=quarantine; adkim=r; aspf=r; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]
• Syntax: Valid
• Policy: quarantine
• Subdomain Policy: quarantine
• Percent: 100%
• RUA (Aggregate Reports): mailto:[email protected]
• RUF (Forensic Reports): mailto:[email protected]
• DKIM Alignment (adkim): Relaxed
• SPF Alignment (aspf): Relaxed

DMARC External Validation:

• Valid external domains: dmarcdefend.com, dmarcdefend.com
• All external domains in your DMARC record are giving permission to send them DMARC reports.