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



X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
23.10.2019 23:47:45


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
pruebahost.com
A
148.163.81.252
Phoenix/Arizona/United States (US) - Input Output Flood LLC
Hostname: we.love.servers.at.ioflood.net
yes
1
0

AAAA

yes


www.pruebahost.com
A
148.163.81.252
Phoenix/Arizona/United States (US) - Input Output Flood LLC
Hostname: we.love.servers.at.ioflood.net
yes
1
0

AAAA

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 22545, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.11.2019, 00:00:00 +, Signature-Inception: 21.10.2019, 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



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 05.11.2019, 17:00:00 +, Signature-Inception: 23.10.2019, 16:00:00 +, KeyTag 22545, Signer-Name: (root)



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 12163, Flags 256



Public Key with Algorithm 8, KeyTag 17708, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 02.11.2019, 18:24:21 +, Signature-Inception: 18.10.2019, 18:19:21 +, 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: pruebahost.com
pruebahost.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 "p0evhr60uu35h31q3amclktg346l2evc" between the hashed NSEC3-owner "p0ev64cloq0qbn7feahukvbvkm5b01bg" and the hashed NextOwner "p0f0c8jrsco717e8ha6ihdd51njs3lba". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner p0ev64cloq0qbn7feahukvbvkm5b01bg.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 27.10.2019, 04:35:23 +, Signature-Inception: 20.10.2019, 03:25:23 +, KeyTag 12163, Signer-Name: com



0 DNSKEY RR found




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


3. Name Servers

DomainNameserverNS-IP
www.pruebahost.com
  v1s1.xundns.com

pruebahost.com
  v1s1.xundns.com
101.64.176.42
Jiaxing Shi/Zhejiang/China (CN) - China Unicom Zhejiang Province Network


X 
222.187.227.147
Qinnan/Jiangsu/China (CN) - Chinanet


X 
222.187.232.75
Qinnan/Jiangsu/China (CN) - Chinanet


 
42.236.73.194
luohe shi/Henan/China (CN) - China Unicom Henan Province Network


 
42.236.82.105
luohe shi/Henan/China (CN) - China Unicom Henan Province Network


 
42.236.82.112
luohe shi/Henan/China (CN) - China Unicom Henan Province Network


  v1s2.xundns.com
101.64.176.42
Jiaxing Shi/Zhejiang/China (CN) - China Unicom Zhejiang Province Network


X 
222.187.227.147
Qinnan/Jiangsu/China (CN) - Chinanet


X 
222.187.232.75
Qinnan/Jiangsu/China (CN) - Chinanet


 
42.236.73.194
luohe shi/Henan/China (CN) - China Unicom Henan Province Network


 
42.236.82.105
luohe shi/Henan/China (CN) - China Unicom Henan Province Network


 
42.236.82.112
luohe shi/Henan/China (CN) - China Unicom Henan Province Network

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:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1571867245
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:11


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


Domain:pruebahost.com
Zone-Name:
Primary:v1s1.xundns.com
Mail:nsadmin.xundns.com
Serial:2697793
Refresh:3600
Retry:600
Expire:86400
TTL:600
num Entries:12


Domain:www.pruebahost.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
• http://pruebahost.com/
148.163.81.252 GZip used - 10581 / 45028 - 76.50 %
200
Warning: Control chars (Ascii 5, 6, 7, 8) found in Html-Content

Html is minified: 135.38 %
0.617
I
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
ETag: "8d740d216413814"
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: *
Access-Control-Allow-Methods: GET, POST
Date: Wed, 23 Oct 2019 21:57:15 GMT
Connection: close
Content-Length: 10581

• http://www.pruebahost.com/
148.163.81.252 GZip used - 10581 / 45028 - 76.50 %
200
Warning: Control chars (Ascii 5, 6, 7, 8) found in Html-Content

Html is minified: 135.38 %
0.610
I
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
ETag: "8d740d216413814"
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: *
Access-Control-Allow-Methods: GET, POST
Date: Wed, 23 Oct 2019 21:57:15 GMT
Connection: close
Content-Length: 10581

• https://pruebahost.com/
148.163.81.252
-2

1.447
V
ConnectFailure - Unable to connect to the remote server

• https://www.pruebahost.com/
148.163.81.252
-2

1.450
V
ConnectFailure - Unable to connect to the remote server

• http://pruebahost.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
148.163.81.252 No GZip used - 232 / 449 - 51.67 % possible
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 151.18 %
2.457

Visible Content: 请求目标站发生错误,当前请求IP:107.189.174.69:0 ****************************异常文本**************************** 【出现时间】:2019/10/24 5:57:21 【异常原因】:请求目标站发生错误,当前请求IP:107.189.174.69:0 【错误代码】:0 【堆栈调用】:错误代码:无法连接到远程服务器 ***************************************************************
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: *
Access-Control-Allow-Methods: GET, POST
Date: Wed, 23 Oct 2019 21:57:21 GMT
Connection: close
Content-Length: 449

• http://www.pruebahost.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
148.163.81.252 No GZip used - 232 / 451 - 51.44 % possible
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 150.84 %
1.794

Visible Content: 请求目标站发生错误,当前请求IP:104.161.117.184:0 ****************************异常文本**************************** 【出现时间】:2019/10/24 5:57:23 【异常原因】:请求目标站发生错误,当前请求IP:104.161.117.184:0 【错误代码】:0 【堆栈调用】:错误代码:无法连接到远程服务器 ***************************************************************
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: *
Access-Control-Allow-Methods: GET, POST
Date: Wed, 23 Oct 2019 21:57:23 GMT
Connection: close
Content-Length: 451

7. Comments


1. General Results, most used to calculate the result

Aname "pruebahost.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
AGood: All ip addresses are public addresses
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
HFatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Vhttps://pruebahost.com/ 148.163.81.252
-2

Connect failure - perhaps firewall
Vhttps://www.pruebahost.com/ 148.163.81.252
-2

Connect failure - perhaps firewall
XFatal error: Nameserver isn't defined or has timeout
XFatal error: Nameserver doesn't support TCP connection: v1s1.xundns.com: Timeout
XFatal error: Nameserver doesn't support TCP connection: v1s1.xundns.com / 101.64.176.42: Timeout
XFatal error: Nameserver doesn't support TCP connection: v1s1.xundns.com / 222.187.227.147: Fatal error (-14). Details: Unable to read data from the transport connection: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat. - Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat
XFatal error: Nameserver doesn't support TCP connection: v1s1.xundns.com / 222.187.232.75: Fatal error (-14). Details: Unable to read data from the transport connection: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat. - Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat
XFatal error: Nameserver doesn't support TCP connection: v1s1.xundns.com / 42.236.73.194: Timeout
XFatal error: Nameserver doesn't support TCP connection: v1s1.xundns.com / 42.236.82.105: Timeout
XFatal error: Nameserver doesn't support TCP connection: v1s1.xundns.com / 42.236.82.112: Timeout
XFatal error: Nameserver doesn't support TCP connection: v1s2.xundns.com / 101.64.176.42: Timeout
XFatal error: Nameserver doesn't support TCP connection: v1s2.xundns.com / 222.187.227.147: Fatal error (-14). Details: Unable to read data from the transport connection: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat. - Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat
XFatal error: Nameserver doesn't support TCP connection: v1s2.xundns.com / 222.187.232.75: Fatal error (-14). Details: Unable to read data from the transport connection: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat. - Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat
XFatal error: Nameserver doesn't support TCP connection: v1s2.xundns.com / 42.236.73.194: Timeout
XFatal error: Nameserver doesn't support TCP connection: v1s2.xundns.com / 42.236.82.105: Timeout
XFatal error: Nameserver doesn't support TCP connection: v1s2.xundns.com / 42.236.82.112: Timeout

2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete)


3. DNS- and NameServer - Checks

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: v1s1.xundns.com,v1s2.xundns.com
AGood: Nameserver supports Echo Capitalization: 12 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
Nameserver doesn't pass all EDNS-Checks: v1s1.xundns.com: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: v1s1.xundns.com / 101.64.176.42: OP100: ok. FLAGS: ok. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: v1s1.xundns.com / 222.187.227.147: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: v1s1.xundns.com / 222.187.232.75: OP100: ok. FLAGS: ok. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: v1s1.xundns.com / 42.236.73.194: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: v1s1.xundns.com / 42.236.82.105: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: v1s2.xundns.com / 101.64.176.42: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: v1s2.xundns.com / 222.187.227.147: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: v1s2.xundns.com / 222.187.232.75: OP100: ok. FLAGS: ok. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: v1s2.xundns.com / 42.236.73.194: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: v1s2.xundns.com / 42.236.82.112: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
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.

4. Content- and Performance-critical Checks

http://pruebahost.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 148.163.81.252
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.pruebahost.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 148.163.81.252
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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: 582574 milliseconds, 582.574 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

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

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.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.pruebahost.com
0

no CAA entry found
1
0
pruebahost.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
pruebahost.com

ok
1
0
www.pruebahost.com

ok
1
0
_acme-challenge.pruebahost.com

missing entry or wrong length
1
0
_acme-challenge.www.pruebahost.com

missing entry or wrong length
1
0
_acme-challenge.pruebahost.com.pruebahost.com

perhaps wrong
1
0
_acme-challenge.www.pruebahost.com.pruebahost.com

perhaps wrong
1
0
_acme-challenge.www.pruebahost.com.www.pruebahost.com

perhaps wrong
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks

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



Permalink: https://check-your-website.server-daten.de/?i=eed6f8c4-1c25-41ed-8554-f11f01fc735e


Last Result: https://check-your-website.server-daten.de/?q=pruebahost.com - 2019-10-23 23:47:45


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

<a href="https://check-your-website.server-daten.de/?q=pruebahost.com" target="_blank">Check this Site: pruebahost.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