Httpfy

DNS Report for sc.gov.br

Date Generated: 2024-09-01 02:41:25
Check Another Domain

Nameservers

  • adns1.pop-sc.rnp.br
    • IPv4: 200.237.192.10
    • IPv6: 2801:80:a88:4000::10
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns3.sc.gov.br
    • IPv4: 200.19.219.9
    • IPv6: 2804:1f00:dc:312:200:19:219:9
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns1.sc.gov.br
    • IPv4: 200.19.215.1
    • IPv6: 2804:1f00:d215:160:200:19:215:1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • adns2.pop-sc.rnp.br
    • IPv4: 200.135.14.10
    • IPv6: 2001:12f0:200:a014::10
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns2.sc.gov.br
    • IPv4: 200.19.215.2
    • IPv6: 2804:1f00:d215:160:200:19:215:2
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A

Nameserver Count - OK

Nameserver Queries

  • adns1.pop-sc.rnp.br
    • Status: Responded
    • IP(s): 200.19.215.161
    • TTL: 3600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns3.sc.gov.br
    • Status: Responded
    • IP(s): 200.19.215.161
    • TTL: 3600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns1.sc.gov.br
    • Status: Responded
    • IP(s): 200.19.215.161
    • TTL: 3600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • adns2.pop-sc.rnp.br
    • Status: Responded
    • IP(s): 200.19.215.161
    • TTL: 3600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns2.sc.gov.br
    • Status: Responded
    • IP(s): 200.19.215.161
    • TTL: 3600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)

SOA Records

adns1.pop-sc.rnp.br
  • Serial: 2024082601
  • Refresh: 3600
  • Retry: 1800
  • Expire: 2419200
  • Minimum TTL: 3600
ns3.sc.gov.br
  • Serial: 2024082601
  • Refresh: 3600
  • Retry: 1800
  • Expire: 2419200
  • Minimum TTL: 3600
ns1.sc.gov.br
  • Serial: 2024082601
  • Refresh: 3600
  • Retry: 1800
  • Expire: 2419200
  • Minimum TTL: 3600
adns2.pop-sc.rnp.br
  • Serial: 2024082601
  • Refresh: 3600
  • Retry: 1800
  • Expire: 2419200
  • Minimum TTL: 3600
ns2.sc.gov.br
  • Serial: 2024082601
  • Refresh: 3600
  • Retry: 1800
  • Expire: 2419200
  • Minimum TTL: 3600

Serial: 2024082601 - OK

REFRESH: 3600 - OK

RETRY: 1800 - OK

EXPIRE: 2419200 - OK

MINIMUM TTL: 3600 - OK

MX Records

adns1.pop-sc.rnp.br
ns3.sc.gov.br
ns1.sc.gov.br
adns2.pop-sc.rnp.br
ns2.sc.gov.br

MX Record Consistency - Warning: Inconsistencies found

MX Record Count - OK

Reverse MX A records (PTR)

  • 27.184.233.64.in-addr.arpa -> wa-in-f27.1e100.net
  • 27.202.85.209.in-addr.arpa -> dg-in-f27.1e100.net
  • 26.202.85.209.in-addr.arpa -> dg-in-f26.1e100.net
  • 27.202.85.209.in-addr.arpa -> dg-in-f27.1e100.net
  • 26.184.233.64.in-addr.arpa -> wa-in-f26.1e100.net
  • 26.184.233.64.in-addr.arpa -> wa-in-f26.1e100.net
  • 27.163.251.142.in-addr.arpa -> wv-in-f27.1e100.net
  • 26.16.251.142.in-addr.arpa -> bl-in-f26.1e100.net
  • 27.184.233.64.in-addr.arpa -> wa-in-f27.1e100.net

PTR Records - OK

DNSSEC

DNSSEC Inspector
  • Signed: Yes
  • Validation: Successful
  • DNSKEY Records: 1
  • DS Records in parent zone: 0
  • DS at Parent: None

DNSSEC - OK

SPF (Sender Policy Framework)

SPF Record Published: Failed

Multiple SPF Records: Passed

Errors:
  • No TXT records found

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

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

Copyright © 2024 HTTPfy Terms & Conditions - Privacy Policy