DNS Report for blazing.de

• ns1.blazing.de

  • IPv4: 213.172.105.106
  • IPv6: 2001:1640:3::53
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

• ns1.cyconet.org

  • IPv4: 217.145.103.249
  • IPv6: 2001:4dc8:9000:1500::53
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

• ns3.waaf.net

  • IPv4: 188.166.73.66
  • IPv6: 2a03:b0c0:2:d0::d83:7001
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

• ns2.blazing.de

  • IPv4: 85.220.190.246
  • IPv6: 2001:1640:11a::2
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

Nameserver Count - OK

• ns1.blazing.de

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

• ns1.cyconet.org

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

• ns3.waaf.net

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

• ns2.blazing.de

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

ns1.blazing.de

• Serial: 2013040426
• Refresh: 14400
• Retry: 3600
• Expire: 604800
• Minimum TTL: 38400

ns1.cyconet.org

• Serial: 2013040426
• Refresh: 14400
• Retry: 3600
• Expire: 604800
• Minimum TTL: 38400

ns3.waaf.net

• Serial: 2013040426
• Refresh: 14400
• Retry: 3600
• Expire: 604800
• Minimum TTL: 38400

ns2.blazing.de

• Serial: 2013040426
• Refresh: 14400
• Retry: 3600
• Expire: 604800
• Minimum TTL: 38400

Serial: 2013040426 - OK

REFRESH: 14400 - OK

RETRY: 3600 - OK

EXPIRE: 604800 - OK

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

ns1.blazing.de

• 10 mail.blazing.de ( 213.172.105.107 )
• 15 ernie.gerger-net.de ( 85.220.190.246 )

ns1.cyconet.org

• 10 mail.blazing.de ( 213.172.105.107 )
• 15 ernie.gerger-net.de ( 85.220.190.246 )

ns3.waaf.net

• 10 mail.blazing.de ( 213.172.105.107 )
• 15 ernie.gerger-net.de ( 85.220.190.246 )

ns2.blazing.de

• 10 mail.blazing.de ( 213.172.105.107 )
• 15 ernie.gerger-net.de ( 85.220.190.246 )

MX Record Consistency - OK

MX Record Count - OK

• 246.190.220.85.in-addr.arpa -> ernie.gerger-net.de
• 107.105.172.213.in-addr.arpa -> mail.blazing.de

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 a mx ip4:213.172.105.104/29 ip6:2001:1640:3::/64 -all
• SPF Syntax: Failed
• Deprecated Elements: Passed
• IP Addresses: 213.172.105.104/29, 2001:1640:3::/64
• Includes:
• DNS Lookups: 3
• Void Lookups: Passed
• Escaping Chars: Not Present
• All Mechanism: -all

Errors:

• SPF record syntax is invalid

• DKIM Records Found: No

Warnings:

• No DKIM records found for common selectors

• Record: v=DMARC1;
• Syntax: Valid
• Policy: None
• RUA (Aggregate Reports):

DMARC External Validation:

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

Warnings:

• Invalid policy: None