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

...

skip EDNS-Check

skip Content-Check

check links

Connect failure - perhaps firewall

Checked:
18.01.2019 13:18:50

Older results

V - 18.01.2019 13:00:59

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
esiconta.com	AAAA		yes
admin.esiconta.com	CNAME	esiconta.com	yes	1	0
	A	37.187.144.223 Hostname: ns3111216.ip-37-187-144.eu	yes
www.admin.esiconta.com		Name Error	yes	1	0

2. DNSSEC

Zone (*)	DNSSEC - Informations

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


	• Status: Valid because published


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 16749, Flags 256


	Public Key with Algorithm 8, KeyTag 19164, Flags 385


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


	2 RRSIG RR to validate DNSKEY RR found


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


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


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


	• 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: com
com	1 DS RR in the parent zone found


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 31.01.2019, 05:00:00 +, Signature-Inception: 18.01.2019, 04:00:00 +, KeyTag 16749, Signer-Name: (root)


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


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 16883, Flags 256


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


	Public Key with Algorithm 8, KeyTag 37490, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.01.2019, 19:25:33 +, Signature-Inception: 12.01.2019, 19:20:33 +, KeyTag 30909, Signer-Name: com


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


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

Zone: esiconta.com
esiconta.com	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: admin.esiconta.com
admin.esiconta.com	0 DS RR in the parent zone found

Zone: www.admin.esiconta.com
www.admin.esiconta.com	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.admin.esiconta.com	• dns15.ovh.net
esiconta.com	• dns15.ovh.net
	• ns15.ovh.net
com	• a.gtld-servers.net
	• b.gtld-servers.net
	• c.gtld-servers.net
	• d.gtld-servers.net
	• e.gtld-servers.net
	• f.gtld-servers.net
	• g.gtld-servers.net
	• h.gtld-servers.net
	• i.gtld-servers.net
	• j.gtld-servers.net
	• k.gtld-servers.net
	• l.gtld-servers.net
	• m.gtld-servers.net

4. SOA-Entries

No SOA informations found. The feature is new (startet 2019-02-05), so recheck this domain.

5. Screenshots

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

6. Url-Checks

Domainname	Http-Status	Sec.	G
• http://admin.esiconta.com/ 37.187.144.223	-2	1.086	V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 37.187.144.223:80

• https://admin.esiconta.com/ 37.187.144.223	-2	1.070	V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 37.187.144.223:443

• http://admin.esiconta.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.187.144.223	-2	1.076	V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 37.187.144.223:80
Visible Content:

7. Comments

	1. General Results, most used to calculate the result
A	name "admin.esiconta.com" is subdomain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
A	Good: All ip addresses are public addresses
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
V	http://admin.esiconta.com/ 37.187.144.223	-2	Connect failure - perhaps firewall
V	https://admin.esiconta.com/ 37.187.144.223	-2	Connect failure - perhaps firewall
V	http://admin.esiconta.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.187.144.223	-2	Connect failure - perhaps firewall
	2. Header-Checks
	3. DNS- and NameServer - Checks
A	Good: Nameserver supports TCP connections: 2 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 2 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
	Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
	4. Content- and Performance-critical Checks
	http://admin.esiconta.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.187.144.223	-2	Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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: 31700 milliseconds, 31.700 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 - Certificate-Transparency-Log informations found. The feature is new (startet 2019-05-07), so recheck this domain.

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

No Certificate-Transparency-Log informations found. The feature is new (startet 2019-03-21), so recheck this domain.

11. Html-Content - Entries

No Html-Content informations found. The feature is new (startet 2019-01-22), so recheck this domain.

12. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.

14. CAA - Entries

Domainname	flag	Value	∑ Queries
admin.esiconta.com			1
esiconta.com	0	no CAA entry found	1
com	0	no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
admin.esiconta.com	1\|www.esiconta.com	ok	1
_acme-challenge.admin.esiconta.com		Name Error - The domain name does not exist	1
_acme-challenge.admin.esiconta.com.admin.esiconta.com		Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No Ciphers found

18. Portchecks

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.

Permalink: https://check-your-website.server-daten.de/?i=ba8a7fea-5c4a-4a29-ad93-d70f3fdc700a

Last Result: https://check-your-website.server-daten.de/?q=admin.esiconta.com - 2019-01-18 13:18:50

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

<a href="https://check-your-website.server-daten.de/?q=admin.esiconta.com" target="_blank">Check this Site: admin.esiconta.com</a>

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

QR-Code of this page - https://check-your-website.server-daten.de/?d=admin.esiconta.com