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


Update: 2020-03-04 - now 90 days later. All affected Letsencrypt certificates should be renewed. Time to remove that Info.




Y

Private IP-Address found

Checked:
22.05.2020 15:24:26


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
nextcloud.emadenergy.com
A
192.168.1.28
No Hostname found
yes
1
0

AAAA

yes


www.nextcloud.emadenergy.com

Name Error
yes
1
0
*.emadenergy.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.nextcloud.emadenergy.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

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



Status: Valid because published



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 48903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.06.2020, 00:00:00, Signature-Inception: 21.05.2020, 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: com
com
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.06.2020, 05:00:00, Signature-Inception: 22.05.2020, 04:00:00, KeyTag 48903, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 39844, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.05.2020, 18:24:21, Signature-Inception: 15.05.2020, 18:19:21, KeyTag 30909, Signer-Name: com



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.05.2020, 18:24:21, Signature-Inception: 15.05.2020, 18:19:21, KeyTag 30909, Signer-Name: com



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



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: emadenergy.com
emadenergy.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "g0td71d11a5879j9no1j3duh4k7ka5cg" between the hashed NSEC3-owner "g0td44nnnefh7n04hau59j3ehq2cbhsd" and the hashed NextOwner "g0tde1k9k39a126055akq2mo71rvsh19". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 27.05.2020, 04:53:14, Signature-Inception: 20.05.2020, 03:43:14, KeyTag 39844, Signer-Name: com



0 DNSKEY RR found




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



0 DNSKEY RR found




Zone: www.nextcloud.emadenergy.com
www.nextcloud.emadenergy.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.nextcloud.emadenergy.com
  ns12.wixdns.net

nextcloud.emadenergy.com
  ns12.wixdns.net
216.239.36.101
Newark/New Jersey/United States (US) - Google LLC

emadenergy.com
  ns12.wixdns.net
216.239.36.101
Newark/New Jersey/United States (US) - Google LLC


  ns13.wixdns.net
216.239.38.101
Ashburn/Virginia/United States (US) - Google LLC

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


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1590153842
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1590153857
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:7


Domain:emadenergy.com
Zone-Name:emadenergy.com
Primary:ns12.wixdns.net
Mail:support.wix.com
Serial:2020042915
Refresh:10800
Retry:3600
Expire:604800
TTL:3600
num Entries:2


Domain:nextcloud.emadenergy.com
Zone-Name:emadenergy.com
Primary:ns12.wixdns.net
Mail:support.wix.com
Serial:2020042915
Refresh:10800
Retry:3600
Expire:604800
TTL:3600
num Entries:1


Domain:www.nextcloud.emadenergy.com
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

DomainnameHttp-StatusredirectSec.G







7. Comments


1. General Results, most used to calculate the result

Aname "nextcloud.emadenergy.com" is subdomain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Ynextcloud.emadenergy.com

192.168.1.28
Warning: Private ip address found. No connection possible. There are two types of ip addresses: Worldwide unique, global addresses and private addresses. If you want that other users connect your domain, your domain must have minimal one A- (ipv4) or AAAA- (ipv6) entry with a global ip address. Check https://en.wikipedia.org/wiki/Private_network to understand the details: 192.168.0.0 to 192.168.255.255: Class C - 256 private net, every with 256 addresses

2. DNS- and NameServer - Checks

AInfo:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 7 Queries complete, 3 with IPv6, 4 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns12.wixdns.net, ns13.wixdns.net, 2 Name Servers included in Delegation: ns12.wixdns.net, ns13.wixdns.net, 2 Name Servers included in 1 Zone definitions: ns12.wixdns.net, ns13.wixdns.net, 1 Name Servers listed in SOA.Primary: ns12.wixdns.net.
AGood: Only one SOA.Primary Name Server found.: ns12.wixdns.net.
AGood: SOA.Primary Name Server included in the delegation set.: ns12.wixdns.net.
AGood: 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: ns12.wixdns.net, ns13.wixdns.net
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 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.: 2 Name Servers, 1 Top Level Domain: net
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: wixdns.net
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 216., 1 different subnets (first two Bytes): 216.239., 2 different subnets (first three Bytes): 216.239.36., 216.239.38.
AGood: Name Server IPv4-addresses from different subnet found:
AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns12.wixdns.net: 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.
AGood: All SOA have the same Serial Number
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.

3. Content- and Performance-critical Checks

AInfo: No img element found, no alt attribute checked
AGood: 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
ADuration: 31910 milliseconds, 31.910 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" > 2019 are listed

No CRT - CT-Log entries found


11. Html-Content - Entries

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


12. Nameserver - IP-Adresses (alpha)

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns12.wixdns.net, ns13.wixdns.net

QNr.DomainTypeNS used
1
net
NS
e.root-servers.net (2001:500:a8::e)

Answer: 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
2
ns12.wixdns.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.p14.dynect.net, ns2.p14.dynect.net, ns3.p14.dynect.net, ns4.p14.dynect.net

Answer: ns1.p14.dynect.net
208.78.70.14

Answer: ns2.p14.dynect.net
204.13.250.14

Answer: ns3.p14.dynect.net
208.78.71.14

Answer: ns4.p14.dynect.net
204.13.251.14
3
ns13.wixdns.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.p14.dynect.net, ns2.p14.dynect.net, ns3.p14.dynect.net, ns4.p14.dynect.net

Answer: ns1.p14.dynect.net
208.78.70.14

Answer: ns2.p14.dynect.net
204.13.250.14

Answer: ns3.p14.dynect.net
208.78.71.14

Answer: ns4.p14.dynect.net
204.13.251.14
4
ns12.wixdns.net: 216.239.36.101
A
ns1.p14.dynect.net (208.78.70.14)
5
ns12.wixdns.net: No AAAA record found
AAAA
ns1.p14.dynect.net (208.78.70.14)
6
ns13.wixdns.net: 216.239.38.101
A
ns1.p14.dynect.net (208.78.70.14)
7
ns13.wixdns.net: No AAAA record found
AAAA
ns1.p14.dynect.net (208.78.70.14)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
nextcloud.emadenergy.com
0

no CAA entry found
1
0
emadenergy.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
emadenergy.com

ok
1
0
nextcloud.emadenergy.com

ok
1
0
_acme-challenge.nextcloud.emadenergy.com

Name Error - The domain name does not exist
1
0
_acme-challenge.nextcloud.emadenergy.com.emadenergy.com

Name Error - The domain name does not exist
1
0
_acme-challenge.nextcloud.emadenergy.com.nextcloud.emadenergy.com

Name Error - The domain name does not exist
1
0


15. Portchecks

Small Code Update - wait one minute



Permalink: https://check-your-website.server-daten.de/?i=c02060f4-3e47-4018-a2ff-5b8e3f9919ad


Last Result: https://check-your-website.server-daten.de/?q=nextcloud.emadenergy.com - 2020-05-22 15:24:26


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

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