Httpfy

DNS Report for punchmedia.ru

Date Generated: 2024-08-31 04:25:16
Check Another Domain

Nameservers

  • ns2.beget.ru
    • IPv4: 185.50.27.12
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns1.beget.ru
    • IPv4: 5.101.159.11
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns2.beget.pro
    • IPv4: 185.50.27.12
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns1.beget.pro
    • IPv4: 5.101.159.11
    • IPv6: No IPv6 found
    • TTL (IPv4): 6 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns2.beget.com
    • IPv4: 185.50.27.12
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns1.beget.com
    • IPv4: 5.101.159.11
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A

Nameserver Count - OK

Nameserver Queries

  • ns2.beget.ru
    • Status: Responded
    • IP(s): 31.128.41.72
    • TTL: 600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns1.beget.ru
    • Status: Responded
    • IP(s): 31.128.41.72
    • TTL: 600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns2.beget.pro
    • Status: Responded
    • IP(s): 31.128.41.72
    • TTL: 600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns1.beget.pro
    • Status: Responded
    • IP(s): 31.128.41.72
    • TTL: 600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns2.beget.com
    • Status: Responded
    • IP(s): 31.128.41.72
    • TTL: 600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns1.beget.com
    • Status: Responded
    • IP(s): 31.128.41.72
    • TTL: 600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)

SOA Records

ns2.beget.ru
  • Serial: 1723552278
  • Refresh: 300
  • Retry: 600
  • Expire: 86400
  • Minimum TTL: 300
ns1.beget.ru
  • Serial: 1723552278
  • Refresh: 300
  • Retry: 600
  • Expire: 86400
  • Minimum TTL: 300
ns2.beget.pro
  • Serial: 1723552278
  • Refresh: 300
  • Retry: 600
  • Expire: 86400
  • Minimum TTL: 300
ns1.beget.pro
  • Serial: 1723552278
  • Refresh: 300
  • Retry: 600
  • Expire: 86400
  • Minimum TTL: 300
ns2.beget.com
  • Serial: 1723552278
  • Refresh: 300
  • Retry: 600
  • Expire: 86400
  • Minimum TTL: 300
ns1.beget.com
  • Serial: 1723552278
  • Refresh: 300
  • Retry: 600
  • Expire: 86400
  • Minimum TTL: 300

Serial: 1723552278 - OK

REFRESH: 300 - OK

RETRY: 600 - OK

EXPIRE: 86400 - OK

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

MX Records

ns2.beget.ru
ns1.beget.ru
ns2.beget.pro
ns1.beget.pro
ns2.beget.com
ns1.beget.com

MX Record Consistency - OK

MX Record Count - Warning: Only one MX record

Reverse MX A records (PTR)

  • 249.21.88.77.in-addr.arpa -> mxfront.stable.qloud-b.yandex.net

PTR Records - OK

DNSSEC

DNSSEC Inspector
  • 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 (Sender Policy Framework)

SPF Record Published: Passed

Multiple SPF Records: Passed

SPF Record 1:
  • Record: v=spf1 redirect=_spf.yandex.net
  • SPF Syntax: Failed
  • Deprecated Elements: Passed
  • IP Addresses:
  • Includes:
  • DNS Lookups: 1
  • Void Lookups: Passed
  • Escaping Chars: Not Present
  • All Mechanism: Not Present
Warnings:
  • SPF record doesn't contain an 'all' mechanism
Errors:
  • SPF record syntax is invalid

DKIM (DomainKeys Identified Mail)

  • DKIM Records Found: Yes
  • Selectors Found: mail
  • Selector 'mail':
    Record: v=DKIM1; k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDFBDopTj3uWehESCMmIu+V+UKQqRblPqunLeGMFAVVvbHXpvxsdFI8kZm8hccyegIB2+otGCdsqOlrFr5wUrlUEu/CqIwbvm62t2PUB1E0iMzpmclFGhxqx00MAmMZB9dEfKZ4J6VktM58GdtIirHtwQVQ447d1e0vEzmA22EGPQIDAQAB
  • Valid Syntax: Yes

DMARC

  • 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
Check DNS for Another Domain

Use our DNS Checker to analyze DNS records for any domain.

Go to DNS Checker

Empower Your Network, Enhance Your DevOps: The Ultimate Online Tools Hub

Copyright © 2024 HTTPfy Terms & Conditions - Privacy Policy