DNS Report for psu.edu

• ns6.psu.edu

  • IPv4: 128.118.70.4
  • IPv6: 2610:8:6800:6::5
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

• ns4.psu.edu

  • IPv4: 128.118.25.5
  • IPv6: 2610:8:7800::4
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

• ns3.psu.edu

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

• ns5.psu.edu

  • IPv4: 128.118.25.4
  • IPv6: 2610:8:7800::5
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

Nameserver Count - OK

• ns6.psu.edu

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

• ns4.psu.edu

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

• ns3.psu.edu

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

• ns5.psu.edu

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

ns6.psu.edu

• Serial: 297835
• Refresh: 3600
• Retry: 600
• Expire: 1209600
• Minimum TTL: 3600

ns4.psu.edu

• Serial: 297835
• Refresh: 3600
• Retry: 600
• Expire: 1209600
• Minimum TTL: 3600

ns3.psu.edu

• Serial: 297835
• Refresh: 3600
• Retry: 600
• Expire: 1209600
• Minimum TTL: 3600

ns5.psu.edu

• Serial: 297835
• Refresh: 3600
• Retry: 600
• Expire: 1209600
• Minimum TTL: 3600

Serial: 297835 - OK

REFRESH: 3600 - OK

RETRY: 600 - OK

EXPIRE: 1209600 - OK

MINIMUM TTL: 3600 - OK

ns6.psu.edu

• 10 psu-edu.mail.protection.outlook.com ( 52.101.9.20 )
• 100 tr10g04.aset.psu.edu ( 128.118.142.105 )
• 100 tr10g05.aset.psu.edu ( 146.186.16.57 )
• 100 tr16g04.aset.psu.edu ( 128.118.142.114 )

ns4.psu.edu

• 10 psu-edu.mail.protection.outlook.com ( 52.101.9.20 )
• 100 tr10g04.aset.psu.edu ( 128.118.142.105 )
• 100 tr10g05.aset.psu.edu ( 146.186.16.57 )
• 100 tr16g04.aset.psu.edu ( 128.118.142.114 )

ns3.psu.edu

• 10 psu-edu.mail.protection.outlook.com ( 52.101.9.12 )
• 100 tr10g04.aset.psu.edu ( 128.118.142.105 )
• 100 tr10g05.aset.psu.edu ( 146.186.16.57 )
• 100 tr16g04.aset.psu.edu ( 128.118.142.114 )

ns5.psu.edu

• 10 psu-edu.mail.protection.outlook.com ( 52.101.41.4 )
• 100 tr10g04.aset.psu.edu ( 128.118.142.105 )
• 100 tr10g05.aset.psu.edu ( 146.186.16.57 )
• 100 tr16g04.aset.psu.edu ( 128.118.142.114 )

MX Record Consistency - Warning: Inconsistencies found

MX Record Count - OK

• 12.9.101.52.in-addr.arpa -> mail-bl0pr05cu00504.inbound.protection.outlook.com
• 57.16.186.146.in-addr.arpa -> tr10g05.aset.psu.edu
• 4.41.101.52.in-addr.arpa -> mail-sj2pr05cu00204.inbound.protection.outlook.com
• 20.9.101.52.in-addr.arpa -> mail-bl0pr02cu00604.inbound.protection.outlook.com
• 105.142.118.128.in-addr.arpa -> tr10g04.aset.psu.edu
• 114.142.118.128.in-addr.arpa -> tr16g04.aset.psu.edu

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 ip4:128.118.0.0/16 ip4:146.186.0.0/16 ip4:130.203.0.0/16 include:cust-spf.cashnet.com ?all
• SPF Syntax: Passed
• Deprecated Elements: Passed
• IP Addresses: 128.118.0.0/16, 146.186.0.0/16, 130.203.0.0/16
• Includes: spf.protection.outlook.com, cust-spf.cashnet.com
• DNS Lookups: 4
• Void Lookups: Passed
• Escaping Chars: Not Present
• All Mechanism: ?all

• DKIM Records Found: Yes
• Selectors Found: default
• Selector 'default':
  Record: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4qg5C0Nqu7U6kGggVa2REdhNNBgcTig1N93vgzLy2k6DGRPqyPjup99d5R+nXrR3U/ZG0g7djR8wih6HvyXxxYUrDJEa0dQ3wBhwodeTQwZ4BK7/S2zbLlb1FWqef0//sZICwlrk84/ZwzJ7qMnQ231TLrZVX022KqkjQGAh8k7q1WAw266ou+eRBB0k5Pxk
• Valid Syntax: Yes

• Record: v=DMARC1; p=none; fo=1; rua=mailto:[email protected],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]
• Failure Options (fo): 1

DMARC External Validation:

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