Httpfy

DNS Report for buff.ly

Date Generated: 2024-09-13 01:36:52

Nameservers

  • ns-1435.awsdns-51.org
    • IPv4: 205.251.197.155
    • IPv6: 2600:9000:5305:9b00::1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns-1542.awsdns-00.co.uk
    • IPv4: 205.251.198.6
    • IPv6: 2600:9000:5306:600::1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns-372.awsdns-46.com
    • IPv4: 205.251.193.116
    • IPv6: 2600:9000:5301:7400::1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns-766.awsdns-31.net
    • IPv4: 205.251.194.254
    • IPv6: 2600:9000:5302:fe00::1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A

Nameserver Count - OK

Nameserver Queries

  • ns-1435.awsdns-51.org
    • Status: Responded
    • IP(s): 67.199.248.12, 67.199.248.13
    • TTL: 20 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns-1542.awsdns-00.co.uk
    • Status: Responded
    • IP(s): 67.199.248.13, 67.199.248.12
    • TTL: 20 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns-372.awsdns-46.com
    • Status: Responded
    • IP(s): 67.199.248.13, 67.199.248.12
    • TTL: 20 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns-766.awsdns-31.net
    • Status: Responded
    • IP(s): 67.199.248.13, 67.199.248.12
    • TTL: 20 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)

SOA Records

ns-1435.awsdns-51.org
  • Serial: 1
  • Refresh: 7200
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 86400
ns-1542.awsdns-00.co.uk
  • Serial: 1
  • Refresh: 7200
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 86400
ns-372.awsdns-46.com
  • Serial: 1
  • Refresh: 7200
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 86400
ns-766.awsdns-31.net
  • Serial: 1
  • Refresh: 7200
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 86400

Serial: 1 - OK

REFRESH: 7200 - OK

RETRY: 900 - OK

EXPIRE: 1209600 - OK

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

MX Records

ns-1435.awsdns-51.org

Error: The DNS response does not contain an answer to the question: buff.ly. IN MX

ns-1542.awsdns-00.co.uk

Error: The DNS response does not contain an answer to the question: buff.ly. IN MX

ns-372.awsdns-46.com

Error: The DNS response does not contain an answer to the question: buff.ly. IN MX

ns-766.awsdns-31.net

Error: The DNS response does not contain an answer to the question: buff.ly. IN MX

MX Record Consistency - OK

MX Record Count - OK

Reverse MX A records (PTR)

No PTR records data available.

  • 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 a mx include:spf1.mcsv.net include:spf.mandrillapp.com include:sendgrid.net include:helpscoutemail.com include:_spf.google.com ~all
  • SPF Syntax: Failed
  • Deprecated Elements: Passed
  • IP Addresses:
  • Includes: spf1.mcsv.net, spf.mandrillapp.com, sendgrid.net, helpscoutemail.com, _spf.google.com
  • DNS Lookups: 11 (Warning: Exceeds limit)
  • Void Lookups: Passed
  • Escaping Chars: Not Present
  • All Mechanism: ~all
Warnings:
  • SPF record has more than 10 DNS lookups, which may cause lookup limits
Errors:
  • SPF record syntax is invalid

DKIM (DomainKeys Identified Mail)

  • DKIM Records Found: No
Warnings:
  • No DKIM records found for common selectors

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