Check DNS, Urls + Redirects, Certificates and Content of your Website

...

skip EDNS-Check

skip Content-Check

check links

Connect failure - perhaps firewall

Checked:
18.09.2023 20:09:19

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
scd.sefaz.to.gov.br	A	128.201.16.201 Palmas/Tocantins/Brazil (BR) - Agencia De Tecnologia DA Informacao No Hostname found	yes	1	0
	AAAA		yes
www.scd.sefaz.to.gov.br		Name Error	yes	1	0
*.sefaz.to.gov.br	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.scd.sefaz.to.gov.br	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes

2. DNSSEC

Zone (*)	DNSSEC - Informations

Zone: (root)
(root)	1 DS RR published


	DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=


	• Status: Valid because published


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 11019, Flags 256


	Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 30.09.2023, 00:00:00 +, Signature-Inception: 09.09.2023, 00:00:00 +, KeyTag 20326, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: br
br	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 2471, DigestType 2 and Digest Xk81mYuPkJVX+hGcTL/cotZgom8GnvAGtAN1igfRouQ=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner br., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.10.2023, 05:00:00 +, Signature-Inception: 18.09.2023, 04:00:00 +, KeyTag 11019, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 11019 used to validate the DS RRSet in the parent zone


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 1926, Flags 256


	Public Key with Algorithm 13, KeyTag 2471, Flags 257 (SEP = Secure Entry Point)


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner br., Algorithm: 13, 1 Labels, original TTL: 21600 sec, Signature-expiration: 08.10.2023, 12:00:00 +, Signature-Inception: 17.09.2023, 12:00:00 +, KeyTag 2471, Signer-Name: br


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 2471 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 2471, DigestType 2 and Digest "Xk81mYuPkJVX+hGcTL/cotZgom8GnvAGtAN1igfRouQ=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: gov.br
gov.br	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 32396, DigestType 2 and Digest J3q4KwfHxusNCNiV8swbvMbpBun/kao6iKoEr72RUvQ=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner gov.br., Algorithm: 13, 2 Labels, original TTL: 21600 sec, Signature-expiration: 29.09.2023, 12:00:10 +, Signature-Inception: 15.09.2023, 11:00:10 +, KeyTag 1926, Signer-Name: br


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 1926 used to validate the DS RRSet in the parent zone


	1 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 32396, Flags 257 (SEP = Secure Entry Point)


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner gov.br., Algorithm: 13, 2 Labels, original TTL: 21600 sec, Signature-expiration: 02.10.2023, 18:05:11 +, Signature-Inception: 18.09.2023, 17:05:11 +, KeyTag 32396, Signer-Name: gov.br


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 32396 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 32396, DigestType 2 and Digest "J3q4KwfHxusNCNiV8swbvMbpBun/kao6iKoEr72RUvQ=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: to.gov.br
to.gov.br	1 DS RR in the parent zone found


	DS with Algorithm 5, KeyTag 2524, DigestType 1 and Digest qU2O6xE1DT1Ac/lqXyy0lN25i7A=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner to.gov.br., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 26.09.2023, 12:01:02 +, Signature-Inception: 12.09.2023, 11:01:02 +, KeyTag 32396, Signer-Name: gov.br


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 32396 used to validate the DS RRSet in the parent zone


	2 DNSKEY RR found


	Public Key with Algorithm 5, KeyTag 2524, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 5, KeyTag 58636, Flags 257 (SEP = Secure Entry Point)


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner to.gov.br., Algorithm: 5, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.10.2023, 12:00:00 +, Signature-Inception: 14.09.2023, 18:17:59 +, KeyTag 2524, Signer-Name: to.gov.br


	RRSIG-Owner to.gov.br., Algorithm: 5, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.10.2023, 12:00:00 +, Signature-Inception: 14.09.2023, 18:17:59 +, KeyTag 58636, Signer-Name: to.gov.br


	• Status: Good - Algorithmus 5 and DNSKEY with KeyTag 2524 used to validate the DNSKEY RRSet


	• Status: Good - Algorithmus 5 and DNSKEY with KeyTag 58636 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 5, KeyTag 2524, DigestType 1 and Digest "qU2O6xE1DT1Ac/lqXyy0lN25i7A=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: sefaz.to.gov.br
sefaz.to.gov.br	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "sefaz.to.gov.br" and the NextOwner "www.sefaz2.to.gov.br". So the parent zone confirmes the non-existence of a DS RR. Bitmap: NS, RRSIG, NSEC


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "sefaz.to.gov.br" and the NextOwner "www.sefaz2.to.gov.br". So the parent zone confirmes the non-existence of a DS RR. Bitmap: NS, RRSIG, NSEC


	1 DNSKEY RR found


	Public Key with Algorithm 5, KeyTag 32971, Flags 257 (SEP = Secure Entry Point)


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner sefaz.to.gov.br., Algorithm: 5, 4 Labels, original TTL: 3600 sec, Signature-expiration: 09.10.2023, 12:00:00 +, Signature-Inception: 05.01.2023, 15:09:18 +, KeyTag 32971, Signer-Name: sefaz.to.gov.br


	• Status: Good - Algorithmus 5 and DNSKEY with KeyTag 32971 used to validate the DNSKEY RRSet


	Error: DNSKEY 32971 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.

Zone: scd.sefaz.to.gov.br
scd.sefaz.to.gov.br	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "scd.sefaz.to.gov.br" and the NextOwner "sgdfiscal-hom.sefaz.to.gov.br". So the parent zone confirmes the non-existence of a DS RR. Bitmap: A, RRSIG, NSEC


	0 DNSKEY RR found





	RRSIG Type 1 validates the A - Result: 128.201.16.201 Validated: RRSIG-Owner scd.sefaz.to.gov.br., Algorithm: 5, 5 Labels, original TTL: 3600 sec, Signature-expiration: 09.10.2023, 12:00:00 +, Signature-Inception: 05.01.2023, 15:09:18 +, KeyTag 32971, Signer-Name: sefaz.to.gov.br


	CNAME-Query sends a valid NSEC RR as result with the query name "scd.sefaz.to.gov.br" equal the NSEC-owner "scd.sefaz.to.gov.br" and the NextOwner "sgdfiscal-hom.sefaz.to.gov.br". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner scd.sefaz.to.gov.br., Algorithm: 5, 5 Labels, original TTL: 3600 sec, Signature-expiration: 09.10.2023, 12:00:00 +, Signature-Inception: 05.01.2023, 15:09:18 +, KeyTag 32971, Signer-Name: sefaz.to.gov.br


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the query name "scd.sefaz.to.gov.br" equal the NSEC-owner "scd.sefaz.to.gov.br" and the NextOwner "sgdfiscal-hom.sefaz.to.gov.br". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner scd.sefaz.to.gov.br., Algorithm: 5, 5 Labels, original TTL: 3600 sec, Signature-expiration: 09.10.2023, 12:00:00 +, Signature-Inception: 05.01.2023, 15:09:18 +, KeyTag 32971, Signer-Name: sefaz.to.gov.br


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "scd.sefaz.to.gov.br" equal the NSEC-owner "scd.sefaz.to.gov.br" and the NextOwner "sgdfiscal-hom.sefaz.to.gov.br". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner scd.sefaz.to.gov.br., Algorithm: 5, 5 Labels, original TTL: 3600 sec, Signature-expiration: 09.10.2023, 12:00:00 +, Signature-Inception: 05.01.2023, 15:09:18 +, KeyTag 32971, Signer-Name: sefaz.to.gov.br


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.scd.sefaz.to.gov.br) sends a valid NSEC RR as result with the owner name scd.sefaz.to.gov.br. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "scd.sefaz.to.gov.br" and the NextOwner "sgdfiscal-hom.sefaz.to.gov.br". So that NSEC confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.scd.sefaz.to.gov.br) sends a valid NSEC RR as result with the query name "_443._tcp.scd.sefaz.to.gov.br" between the NSEC-owner "scd.sefaz.to.gov.br" and the NextOwner "sgdfiscal-hom.sefaz.to.gov.br". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.scd.sefaz.to.gov.br) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.scd.sefaz.to.gov.br" between the NSEC-owner "scd.sefaz.to.gov.br" and the NextOwner "sgdfiscal-hom.sefaz.to.gov.br". So the zone confirmes the not-existence of that Wildcard-expansion. Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner scd.sefaz.to.gov.br., Algorithm: 5, 5 Labels, original TTL: 3600 sec, Signature-expiration: 09.10.2023, 12:00:00 +, Signature-Inception: 05.01.2023, 15:09:18 +, KeyTag 32971, Signer-Name: sefaz.to.gov.br


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "scd.sefaz.to.gov.br" equal the NSEC-owner "scd.sefaz.to.gov.br" and the NextOwner "sgdfiscal-hom.sefaz.to.gov.br". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner scd.sefaz.to.gov.br., Algorithm: 5, 5 Labels, original TTL: 3600 sec, Signature-expiration: 09.10.2023, 12:00:00 +, Signature-Inception: 05.01.2023, 15:09:18 +, KeyTag 32971, Signer-Name: sefaz.to.gov.br


	Status: Good. NoData-Proof required and found.

Zone: www.scd.sefaz.to.gov.br
www.scd.sefaz.to.gov.br	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "scd.sefaz.to.gov.br" and the NextOwner "sgdfiscal-hom.sefaz.to.gov.br". So the parent zone confirmes the non-existence of a DS RR. Bitmap: A, RRSIG, NSEC

3. Name Servers

Domain	Nameserver	NS-IP
www.scd.sefaz.to.gov.br	• ns.to.gov.br
scd.sefaz.to.gov.br	• ns.to.gov.br	128.201.16.20 Palmas/Tocantins/Brazil (BR) - Agencia De Tecnologia DA Informacao	•
	•	131.72.217.1 Palmas/Tocantins/Brazil (BR) - Nova Telecom Ltda	•
	•	131.72.217.20 Palmas/Tocantins/Brazil (BR) - Nova Telecom Ltda	•
	•	191.223.64.1 Palmas/Tocantins/Brazil (BR) - V tal	•
	•	191.223.64.20 Palmas/Tocantins/Brazil (BR) - V tal	•
sefaz.to.gov.br	• ns.to.gov.br	128.201.16.20 Palmas/Tocantins/Brazil (BR) - Agencia De Tecnologia DA Informacao	•
	•	131.72.217.1 Palmas/Tocantins/Brazil (BR) - Nova Telecom Ltda	•
	•	131.72.217.20 Palmas/Tocantins/Brazil (BR) - Nova Telecom Ltda	•
	•	191.223.64.1 Palmas/Tocantins/Brazil (BR) - V tal	•
	•	191.223.64.20 Palmas/Tocantins/Brazil (BR) - V tal	•
	• ns1.to.gov.br	128.201.16.20 Palmas/Tocantins/Brazil (BR) - Agencia De Tecnologia DA Informacao	•
	• ns2.to.gov.br	131.72.217.1 Palmas/Tocantins/Brazil (BR) - Nova Telecom Ltda	•
	• ns3.to.gov.br	191.223.64.20 Palmas/Tocantins/Brazil (BR) - V tal	•
	• ns4.to.gov.br	131.72.217.20 Palmas/Tocantins/Brazil (BR) - Nova Telecom Ltda	•
to.gov.br	• ns.to.gov.br	128.201.16.20 Palmas/Tocantins/Brazil (BR) - Agencia De Tecnologia DA Informacao	•
	•	131.72.217.1 Palmas/Tocantins/Brazil (BR) - Nova Telecom Ltda	•
	•	131.72.217.20 Palmas/Tocantins/Brazil (BR) - Nova Telecom Ltda	•
	•	191.223.64.1 Palmas/Tocantins/Brazil (BR) - V tal	•
	•	191.223.64.20 Palmas/Tocantins/Brazil (BR) - V tal	•
	• ns1.to.gov.br	128.201.16.20 Palmas/Tocantins/Brazil (BR) - Agencia De Tecnologia DA Informacao	•
	• ns2.to.gov.br	131.72.217.1 Palmas/Tocantins/Brazil (BR) - Nova Telecom Ltda	•
	• ns3.to.gov.br	191.223.64.20 Palmas/Tocantins/Brazil (BR) - V tal	•
	• ns4.to.gov.br	131.72.217.20 Palmas/Tocantins/Brazil (BR) - Nova Telecom Ltda	•
gov.br	• a.dns.br / a7.a.dns.br	200.219.148.10 São Paulo/Brazil (BR) - Núcleo de Inf. e Coord. do Ponto BR - NIC.BR	•
	•	2001:12f8:6::10 São Paulo/Brazil (BR) - Núcleo de Inf. e Coord. do Ponto BR - NIC.BR	•
	• b.dns.br / b3.b.dns.br	200.189.41.10 Pinheiros/Sao Paulo/Brazil (BR) - Núcleo de Inf. e Coord. do Ponto BR - NIC.BR	•
	•	2001:12f8:8::10 Pinheiros/Sao Paulo/Brazil (BR) - Núcleo de Inf. e Coord. do Ponto BR - NIC.BR	•
	• c.dns.br / c5.c.dns.br	200.192.233.10 Pinheiros/Sao Paulo/Brazil (BR) - Núcleo de Inf. e Coord. do Ponto BR - NIC.BR	•
	•	2001:12f8:a::10 Pinheiros/Sao Paulo/Brazil (BR) - Núcleo de Inf. e Coord. do Ponto BR - NIC.BR	•
	• d.dns.br / d2.d.dns.br	200.219.154.10 Pinheiros/Sao Paulo/Brazil (BR) - Núcleo de Inf. e Coord. do Ponto BR - NIC.BR	•
	•	2001:12f8:4::10 Pinheiros/Sao Paulo/Brazil (BR) - Núcleo de Inf. e Coord. do Ponto BR - NIC.BR	•
	• e.dns.br / e4.e.dns.br	200.229.248.10 Pinheiros/Sao Paulo/Brazil (BR) - Núcleo de Inf. e Coord. do Ponto BR - NIC.BR	•
	•	2001:12f8:2::10 Pinheiros/Sao Paulo/Brazil (BR) - Núcleo de Inf. e Coord. do Ponto BR - NIC.BR	•
	• f.dns.br / f7.a.f.dns.br	200.219.159.10 Pinheiros/Sao Paulo/Brazil (BR) - Núcleo de Inf. e Coord. do Ponto BR - NIC.BR	•
	•	2001:12f8:c::10 Pinheiros/Sao Paulo/Brazil (BR) - Núcleo de Inf. e Coord. do Ponto BR - NIC.BR	•
br	• a.dns.br / a6.a.dns.br		•
	• b.dns.br / b7.b.dns.br		•
	• c.dns.br / c8.c.dns.br		•
	• d.dns.br / d4.d.dns.br		•
	• e.dns.br / e7.e.dns.br		•
	• f.dns.br / f7.a.f.dns.br		•

4. SOA-Entries

Domain:	br
Zone-Name:	br
Primary:	a.dns.br
Mail:	hostmaster.registro.br
Serial:	2023261434
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	900
num Entries:	6

Domain:	gov.br
Zone-Name:	gov.br
Primary:	a.dns.br
Mail:	hostmaster.registro.br
Serial:	2023261434
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	900
num Entries:	12

Domain:	to.gov.br
Zone-Name:	to.gov.br
Primary:	ns.to.gov.br
Mail:	abuse.to.gov.br
Serial:	2023091400
Refresh:	3600
Retry:	900
Expire:	1209600
TTL:	3600
num Entries:	9

Domain:	sefaz.to.gov.br
Zone-Name:	sefaz.to.gov.br
Primary:	ns.to.gov.br
Mail:	abuse.to.gov.br
Serial:	2023090501
Refresh:	3600
Retry:	900
Expire:	1209600
TTL:	3600
num Entries:	9

Domain:	scd.sefaz.to.gov.br
Zone-Name:	sefaz.to.gov.br
Primary:	ns.to.gov.br
Mail:	abuse.to.gov.br
Serial:	2023090501
Refresh:	3600
Retry:	900
Expire:	1209600
TTL:	3600
num Entries:	5

Domain:	www.scd.sefaz.to.gov.br
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://scd.sefaz.to.gov.br/ 128.201.16.201	301	https://scd.sefaz.to.gov.br/ Html is minified: 109.46 %	0.570	A
Server: nginx
Date: Mon, 18 Sep 2023 18:14:36 GMT
Content-Type: text/html
Content-Length: 162
Connection: close
Location: https://scd.sefaz.to.gov.br/

• https://scd.sefaz.to.gov.br/ 128.201.16.201	-2		1.790	V
ConnectFailure - Unable to connect to the remote server

• http://scd.sefaz.to.gov.br/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 128.201.16.201 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 110.61 %	0.514	A
Not Found
Visible Content: 404 Not Found nginx
Server: nginx
Date: Mon, 18 Sep 2023 18:14:39 GMT
Content-Type: text/html
Content-Length: 146
Connection: close

• https://128.201.16.201/ 128.201.16.201	-2		1.743	V
ConnectFailure - Unable to connect to the remote server

7. Comments

	1. General Results, most used to calculate the result
A	name "scd.sefaz.to.gov.br" is subdomain, public suffix is ".to.gov.br", top-level-domain is ".br", top-level-domain-type is "country-code", Country is Brazil, tld-manager is "Comite Gestor da Internet no Brasil", num .br-domains preloaded: 2925 (complete: 231048)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: scd.sefaz.to.gov.br has only one ip address.
	Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: scd.sefaz.to.gov.br has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
A	Good: No cookie sent via http.
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
A	Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (1 urls)
	http://scd.sefaz.to.gov.br/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 128.201.16.201		Url with incomplete Content-Type - header - missing charset
C	Error - no version with Http-Status 200
H	Fatal error: No https - result with http-status 200, no encryption
V	https://scd.sefaz.to.gov.br/ 128.201.16.201	-2	Connect failure - perhaps firewall
V	https://128.201.16.201/ 128.201.16.201	-2	Connect failure - perhaps firewall
	Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain scd.sefaz.to.gov.br, 1 ip addresses.
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.scd.sefaz.to.gov.br
	2. Header-Checks
U			No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 5 Name Servers.
A	Info:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
A	Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns.to.gov.br (191.223.64.1), ns1.to.gov.br (128.201.16.20), ns2.to.gov.br (131.72.217.1), ns3.to.gov.br (191.223.64.20), ns4.to.gov.br (131.72.217.20)
A	Good (1 - 3.0):: An average of 0.4 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 5 different Name Servers found: ns.to.gov.br, ns1.to.gov.br, ns2.to.gov.br, ns3.to.gov.br, ns4.to.gov.br, 5 Name Servers included in Delegation: ns.to.gov.br, ns1.to.gov.br, ns2.to.gov.br, ns3.to.gov.br, ns4.to.gov.br, 5 Name Servers included in 1 Zone definitions: ns.to.gov.br, ns1.to.gov.br, ns2.to.gov.br, ns3.to.gov.br, ns4.to.gov.br, 1 Name Servers listed in SOA.Primary: ns.to.gov.br.
A	Good: Only one SOA.Primary Name Server found.: ns.to.gov.br.
A	Good: SOA.Primary Name Server included in the delegation set.: ns.to.gov.br.
A	Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns.to.gov.br, ns1.to.gov.br, ns2.to.gov.br, ns3.to.gov.br, ns4.to.gov.br
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 5 different Name Servers found
	Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 5 different Name Servers found
	Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 5 Name Servers, 1 Top Level Domain: to.gov.br
	Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used:
	Warning: All Name Servers from the same Country / IP location.: 5 Name Servers, 1 Countries: BR
A	Info: Ipv4-Subnet-list: 9 Name Servers, 3 different subnets (first Byte): 128., 131., 191., 3 different subnets (first two Bytes): 128.201., 131.72., 191.223., 3 different subnets (first three Bytes): 128.201.16., 131.72.217., 191.223.64.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Good: Nameserver supports TCP connections: 5 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 5 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 5 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 5 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns.to.gov.br: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
A	Good: All SOA have the same Serial Number
A	Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
A	Good: CAA entries found, creating certificate is limited: serpro.gov.br is allowed to create certificates
	Warning: Unknown CAA found: serpro.gov.br isn't defined. Unknown entry. May be wrong written, may be not longer valid. May be a missing entry in this tool.
	4. Content- and Performance-critical Checks
A	Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
A	Info: No img element found, no alt attribute checked
A	Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
A	Duration: 334790 milliseconds, 334.790 seconds

8. Connections

No connection informations found. Perhaps only http - connections.

9. Certificates

No certificate informations found. Perhaps only http - connections.

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - CT-Log entries found

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

Issuer				last 7 days	active	num Certs
CN=R3, O=Let's Encrypt, C=US				0 /0 new	0	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
9065567478 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-04-02 19:04:55	2023-07-01 19:04:54	scd.sefaz.to.gov.br 1 entries

11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404

12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns.to.gov.br, ns1.to.gov.br, ns2.to.gov.br, ns3.to.gov.br, ns4.to.gov.br

QNr.	Domain	Type	NS used
1	br	NS	b.root-servers.net (2001:500:200::b)
	Answer: a.dns.br, b.dns.br, c.dns.br, d.dns.br, e.dns.br, f.dns.br
2	ns.to.gov.br: 191.223.64.1	NS	a.dns.br (2001:12f8:6::10)
	Answer: ns1.to.gov.br 128.201.16.20
	Answer: ns2.to.gov.br 131.72.217.1
	Answer: ns3.to.gov.br 191.223.64.20
	Answer: ns4.to.gov.br 131.72.217.20

13. CAA - Entries

Domainname	flag	Name	Value	∑ Queries
scd.sefaz.to.gov.br	0		no CAA entry found	1
sefaz.to.gov.br	0		no CAA entry found	1
to.gov.br	5	issue	letsencrypt.org	1
	5	issue	serpro.gov.br	1
gov.br	0		no CAA entry found	1
br	0		no CAA entry found	1

14. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
sefaz.to.gov.br	google-site-verification=hdI5CGZiBIpUN6829CId_RWAbDnwrTcb90ZFN-C5nAQ	ok	1
sefaz.to.gov.br	google-site-verification=nThC3uAuD6PABLSjIV9_XsI14zgRCd-BUc8Z69zYsXw	ok	1
sefaz.to.gov.br	v=spf1 include:_spf.google.com ~all	ok	1
sefaz.to.gov.br	workplace-domain-verification=Z5PUUJJ56Vi84BQ1t4T2Byi2UzoBnK	ok	1
scd.sefaz.to.gov.br		ok	1
_acme-challenge.scd.sefaz.to.gov.br		Name Error - The domain name does not exist	1
_acme-challenge.scd.sefaz.to.gov.br.sefaz.to.gov.br		Name Error - The domain name does not exist	1
_acme-challenge.scd.sefaz.to.gov.br.scd.sefaz.to.gov.br		Name Error - The domain name does not exist	1

15. DomainService - Entries

No DomainServiceEntries entries found

16. Cipher Suites

No results

17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

Permalink: https://check-your-website.server-daten.de/?i=decb4c49-73a4-4983-8d76-c8400911187c

Last Result: https://check-your-website.server-daten.de/?q=scd.sefaz.to.gov.br - 2023-09-18 20:09:19

Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=scd.sefaz.to.gov.br" target="_blank">Check this Site: scd.sefaz.to.gov.br</a>

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro